Re: 回复: [External Mail][PATCH] tick/broadcast: Plug clockevents replacement race

[Bradley Morgan]

On 6 September 2026 00:15:28 BST, Thomas Gleixner <tglx@xxxxxxxxxxxxx>
wrote:
>On Sat, Sep 05 2026 at 23:06, Bradley Morgan wrote:
>> On 5 September 2026 23:00:05 BST, Thomas Gleixner <tglx@xxxxxxxxxxxxx>
>> wrote:
>>>On Sat, Sep 05 2026 at 22:24, Bradley Morgan wrote:
>>>> On 5 September 2026 22:21:24 BST, Thomas Gleixner <tglx@xxxxxxxxxxxxx>
>>>wrote:
>>>>>On Thu, Sep 03 2026 at 16:12, Bradley Morgan wrote:
>>>>>> Hi, I have a pixel 7, if I could be asked to backport this, then
>I'll
>>>be
>>>>>> happy to, for the fix, add:
>>>>>>
>>>>>> Reviewed-by: Bradley Morgan <brads@xxxxxxxxxxxxxx>
>>>>>
>>>>>It would be helpful to respond to the actual patch and not to some
>>>>>arbitrary reply. That way you might avoid your tags to be overseen by
>>>>>tools.
>>>>>
>>>> Sorry my mail client sometimes glitches,
>>>
>>>I fail to see how your mail client is responsible for you to hit reply
>>>on the wrong mail.
>>>
>>>But what do I know about all these new fangled mail clients who decide
>>>on their own what to do. When this happens to me I'm 100% confident that
>>>_I_ got it wrong and not my mail client. Maybe I'm just too old-school.
>>>
>> Remove Daniel too. Bounces.
>
>Sorry no. That's not how this works
>
> #1 An OOO response is purely informational and does not justify to
>    remove the recipient from the CC list just because
>
> #2 A bouncing email address is of course a valid reason to remove
>    someone from CC, but it is a matter of courtesy in the context of
>    the Linux kernel lists to lookup whether the person vansished from
>    the planet or just changed the mail address. That's what the
>    MAINTAINERS file is for.
>
>    The thread you responded to was from TWO years ago...
>
>Aside of that you did not respond to my actual complaint about
>responding to a random reply instead of responding to the actual patch.
>
>If you fail to review what the AI agent of your choice hallucinates
>then so be it, but don't be surprised that I'm going to put you on my
>ignore list as a consequence and recommend to all other maintainers to
>do so as well.
>
>   Thomas
>
>
>
oh crap, I see it now. I thought it was a recent thread cause of my lore
search!


Probably:

https://lore.kernel.org/all/87qzj74dxi.ffs@fw13/ ?
--- Thanks!
https://lore.kernel.org/all/EE579805-42F2-4C58-B752-F28779EEB717@xxxxxxxxx/