From: 刘术高 <liushugao@xiaomi.com>
To: "Thomas Gleixner" <tglx@linutronix.de>,
朱恺乾 <zhukaiqian@xiaomi.com>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
'张嘉伟' <zhangjiawei8@xiaomi.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
王韬 <lingyue@xiaomi.com>, 熊亮 <xiongliang@xiaomi.com>,
"isaacmanjarres@google.com" <isaacmanjarres@google.com>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Anna-Maria Behnsen" <anna-maria@linutronix.de>,
梁伟鹏 <weipengliang@xiaomi.com>, 翁金飞 <wengjinfei@xiaomi.com>
Subject: 回复: 回复: [External Mail][PATCH] tick/broadcast: Plug clockevents replacement race
Date: Mon, 7 Sep 2026 06:24:43 +0000 [thread overview]
Message-ID: <cecc2fe0ba9d4ada96b68a12cef0612d@xiaomi.com> (raw)
In-Reply-To: <87jyoz4cs5.ffs@fw13>
On Thu, Sep 03 2026 at 06:33, Thomas Gleixner wrote:
> It took you more than fricking TWO YEARS to test and validate that
> patch and now that you finally came around to take care of it without
> following the documented process you expect me to merge it within a
> couple of days and preferrably expedite it and provide you the
> expected timeline because you have a business case.
You are right. The delay is entirely on our side, and I should not
have requested expediting or a timeline. I apologize for that.
Tested-by: 刘术高 <liushugao@xiaomi.com>
I will make sure to follow the documented process and respond more
promptly in the future.
Thanks,
刘术高
-----邮件原件-----
发件人: Thomas Gleixner <tglx@linutronix.de>
发送时间: 2026年9月6日 5:19
收件人: 刘术高 <liushugao@xiaomi.com>; 朱恺乾 <zhukaiqian@xiaomi.com>; Daniel Lezcano <daniel.lezcano@linaro.org>; '张嘉伟' <zhangjiawei8@xiaomi.com>
抄送: linux-kernel@vger.kernel.org; 王韬 <lingyue@xiaomi.com>; 熊亮 <xiongliang@xiaomi.com>; isaacmanjarres@google.com; Frederic Weisbecker <frederic@kernel.org>; Anna-Maria Behnsen <anna-maria@linutronix.de>; 梁伟鹏 <weipengliang@xiaomi.com>; 翁金飞 <wengjinfei@xiaomi.com>
主题: Re: 回复: [External Mail][PATCH] tick/broadcast: Plug clockevents replacement race
[外部邮件] 此邮件来源于小米公司外部,请谨慎处理。若对邮件安全性存疑,请将邮件转发给misec@xiaomi.com进行反馈
On Thu, Sep 03 2026 at 06:33, 刘术高 wrote:
> Could you please share the expected timeline for merging this fix into
> the mainline kernel? We have downstream products depending on this fix
> and would appreciate it if the merge could be expedited.
Just for the record. Here is the timeline:
2024-06-26: Issue reported
2024-08-12: Patch available after some discussion
2026-08-28: Confirmation that the patch works
2026-09-05: Request for time line
It took you more than fricking TWO YEARS to test and validate that patch and now that you finally came around to take care of it without following the documented process you expect me to merge it within a couple of days and preferrably expedite it and provide you the expected timeline because you have a business case.
IOW, this could have been fixed TWO YEARS ago if you wold have paid attention.
Seriously?
Thanks,
tglx
next prev parent reply other threads:[~2026-09-07 6:25 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
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 ` 刘术高 [this message]
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=cecc2fe0ba9d4ada96b68a12cef0612d@xiaomi.com \
--to=liushugao@xiaomi.com \
--cc=anna-maria@linutronix.de \
--cc=daniel.lezcano@linaro.org \
--cc=frederic@kernel.org \
--cc=isaacmanjarres@google.com \
--cc=lingyue@xiaomi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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®