Message ID | CACRpkdb8dwq7OYUFuyjJCv7VN9mH1zEmibcOwgFip0wDv5H1gA@mail.gmail.com |
---|---|
State | New |
Headers | show |
Series | [GIT,PULL] Pin control fixes for v6.7 minus one patch | expand |
On Wed, 29 Nov 2023 at 07:18, Linus Walleij <linus.walleij@linaro.org> wrote: > > Here is an updated tag on a branch where the only change > is to drop the locking READ_ONCE() patch until we know > more about what is going on here. Bah. I already pulled the previous one and pushed out before reading more emails and noticing you had so quickly re-done it. So the READ_ONCE() workaround is there now, but I hope there will be a future patch that explains (and fixes) whatever made the value change from underneath that code. Linus
On Wed, Nov 29, 2023 at 4:48 PM Linus Torvalds <torvalds@linux-foundation.org> wrote: > On Wed, 29 Nov 2023 at 07:18, Linus Walleij <linus.walleij@linaro.org> wrote: > > > > Here is an updated tag on a branch where the only change > > is to drop the locking READ_ONCE() patch until we know > > more about what is going on here. > > Bah. I already pulled the previous one and pushed out before reading > more emails and noticing you had so quickly re-done it. > > So the READ_ONCE() workaround is there now, but I hope there will be a > future patch that explains (and fixes) whatever made the value change > from underneath that code. Fair enough, we'll look closer at it. I just hope I get some help with that from Maria. Yours, Linus Walleij