From: Thomas Gleixner <tglx@linutronix.de>
To: Bradley Morgan <brads@mainlining.org>, liushugao@xiaomi.com
Cc: frederic@kernel.org, isaacmanjarres@google.com,
lingyue@xiaomi.com, linux-kernel@vger.kernel.org,
weipengliang@xiaomi.com, wengjinfei@xiaomi.com,
xiongliang@xiaomi.com, zhangjiawei8@xiaomi.com,
zhukaiqian@xiaomi.com, Daniel Lezcano <daniel.lezcano@kernel.org>
Subject: Re: 回复: [External Mail][PATCH] tick/broadcast: Plug clockevents replacement race
Date: Sun, 06 Sep 2026 01:15:28 +0200 [thread overview]
Message-ID: <8733vn47e7.ffs@fw13> (raw)
In-Reply-To: <347CE2FE-3675-44AA-80D4-1CF8632C8C9D@mainlining.org>
On Sat, Sep 05 2026 at 23:06, Bradley Morgan wrote:
> On 5 September 2026 23:00:05 BST, Thomas Gleixner <tglx@linutronix.de>
> wrote:
>>On Sat, Sep 05 2026 at 22:24, Bradley Morgan wrote:
>>> On 5 September 2026 22:21:24 BST, Thomas Gleixner <tglx@linutronix.de>
>>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@mainlining.org>
>>>>
>>>>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
next prev parent reply other threads:[~2026-09-05 23:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <042520850d394f0bb0004a226db63d0d@xiaomi.com>
2024-06-27 11:26 ` Race condition when replacing the broadcast timer Thomas Gleixner
2024-06-28 1:59 ` [External Mail]Re: " 朱恺乾
2024-06-28 7:22 ` Daniel Lezcano
2024-07-01 2:11 ` 朱恺乾
2024-07-10 20:30 ` Thomas Gleixner
2024-07-29 11:44 ` Thomas Gleixner
2024-08-12 14:19 ` [PATCH] tick/broadcast: Plug clockevents replacement race Thomas Gleixner
2024-09-25 9:45 ` Anna-Maria Behnsen
2024-10-17 16:16 ` Frederic Weisbecker
2026-09-05 20:54 ` Thomas Gleixner
2026-08-28 9:08 ` 回复: [External Mail][PATCH] " 刘术高
2026-09-03 6:33 ` 刘术高
2026-09-03 15:12 ` Bradley Morgan
2026-09-05 21:21 ` Thomas Gleixner
2026-09-05 21:24 ` Bradley Morgan
2026-09-05 22:00 ` Thomas Gleixner
2026-09-05 22:06 ` Bradley Morgan
2026-09-05 23:15 ` Thomas Gleixner [this message]
2026-09-06 10:40 ` Bradley Morgan
2026-09-05 22:05 ` Thomas Gleixner
2026-09-05 21:19 ` Thomas Gleixner
2026-09-07 6:24 ` 回复: " 刘术高
2026-09-05 20:59 ` Thomas Gleixner
2026-09-07 9:15 ` [tip: timers/urgent] " tip-bot2 for Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8733vn47e7.ffs@fw13 \
--to=tglx@linutronix.de \
--cc=brads@mainlining.org \
--cc=daniel.lezcano@kernel.org \
--cc=frederic@kernel.org \
--cc=isaacmanjarres@google.com \
--cc=lingyue@xiaomi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liushugao@xiaomi.com \
--cc=weipengliang@xiaomi.com \
--cc=wengjinfei@xiaomi.com \
--cc=xiongliang@xiaomi.com \
--cc=zhangjiawei8@xiaomi.com \
--cc=zhukaiqian@xiaomi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®