From: Yaxiong Tian <iambestgod@qq.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Lukasz Luba <lukasz.luba@arm.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Yaxiong Tian <tianyaxiong@kylinos.cn>,
rafael@kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: [PATCH v2] PM: EM: Fix potential division-by-zero error in em_compute_costs()
Date: Thu, 17 Apr 2025 15:41:58 +0800 [thread overview]
Message-ID: <tencent_7F0AB62F9DA4BF9F250063A7421F23AC3908@qq.com> (raw)
In-Reply-To: <CAMuHMdVAvMuzmn48aVB-xshMjbENXFc1MmYB=r7iPrMvfDZjDg@mail.gmail.com>
在 2025/4/17 15:20, Geert Uytterhoeven 写道:
> Hi Yaxiong,
>
> On Mon, 14 Apr 2025 at 11:14, Yaxiong Tian <iambestgod@qq.com> wrote:
>> I wasn’t sure whether the new patch should reuse the current Message-ID
>> or create a new one, so I checked with ChatGPT and kept the original
>> Message-ID for v2. If a new Message-ID is required, I can resend the
>> email.
>
> Different (revisions of) patches must have different Message-IDs,
> else they can no longer be distinguished by our tooling.
> Fortunately it seems like you didn't succeed (which is good ;-),
> as all four revisions do have different Message-IDs:
>
> https://lore.kernel.org/all/tencent_8478BF8F2549630842D323E7394CB6F49D08@qq.com/
> https://lore.kernel.org/all/tencent_EE27C7D1D6BDB3EE57A2C467CC59A866C405@qq.com/
> https://lore.kernel.org/all/tencent_6D2374392DB66C9D23BF6E2546638A42EC08@qq.com/
> https://lore.kernel.org/all/tencent_2256A7C02F7849F1D89390E488704E826D06@qq.com/
>
> Gr{oetje,eeting}s,
>
> Geert
>
Thank you for your explanation. My previous description might have been
a bit unclear. Actually, what I meant was whether it should be --in-
reply-to=original Message-ID. I think if it's a patch, replying to the
original Message-ID would be better.
next prev parent reply other threads:[~2025-04-17 7:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 1:28 Yaxiong Tian
2025-04-12 1:55 ` kernel test robot
2025-04-14 8:08 ` Lukasz Luba
2025-04-14 9:08 ` Yaxiong Tian
2025-04-17 7:20 ` Geert Uytterhoeven
2025-04-17 7:41 ` Yaxiong Tian [this message]
2025-04-15 1:12 ` Yaxiong Tian
2025-04-15 1:58 ` Yaxiong Tian
2025-04-15 17:19 ` Rafael J. Wysocki
2025-04-14 9:04 ` [PATCH v3] " Yaxiong Tian
2025-04-15 8:50 ` Lukasz Luba
2025-04-15 17:17 ` Rafael J. Wysocki
2025-04-16 2:56 ` Yaxiong Tian
2025-04-16 11:58 ` Rafael J. Wysocki
2025-04-16 15:26 ` Lukasz Luba
2025-04-17 0:56 ` Yaxiong Tian
2025-04-17 1:07 ` [PATCH v4] " Yaxiong Tian
2025-04-17 5:57 ` Lukasz Luba
2025-04-17 7:43 ` Yaxiong Tian
2025-04-17 13:27 ` Lukasz Luba
2025-04-18 1:26 ` Yaxiong Tian
2025-04-28 1:45 ` Yaxiong Tian
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=tencent_7F0AB62F9DA4BF9F250063A7421F23AC3908@qq.com \
--to=iambestgod@qq.com \
--cc=geert@linux-m68k.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=tianyaxiong@kylinos.cn \
/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®