On Mon, Mar 21, 2022 at 8:46 AM Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:
>
> This landing in -next only today (after having been committed last
> friday night) is another clue it should probably go next round.
I went and looked at lore to get the context that I didn't get in this
email that I was added to the participants for.
I didn't find the context there either.
Sure, I found the thread, but the whole "that x86 patch" that you
refer to was never actually specified even in the full thread as far
as I can tell. I see that there is an arm64 equivalent too of what you
are complaining about, and I have no idea about that one either..
Mind actually giving the full details so that we don't have to go
re-do the work you already did?
Because right now I know something is wrong, I know the warnings, but
I don't actually have any handle on the actual patches to look out
for.
It's presumably not in any of the pull requests I already have
pending, but it would be nice if I saw some details of _what_ you are
complaining about, and not just the complaint itself ;)
Linus
