From: Thorsten Blum <thorsten.blum@linux.dev>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "Madhavan Srinivasan" <maddy@linux.ibm.com>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Naveen N Rao" <naveen@kernel.org>,
"\"Ricardo B. Marlière\"" <ricardo@marliere.net>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] powerpc: mpic: Use str_enabled_disabled() helper function
Date: Mon, 24 Feb 2025 15:09:19 +0100 [thread overview]
Message-ID: <AE3E083C-D554-449B-9C67-81556D06FD35@linux.dev> (raw)
In-Reply-To: <f872c2ef-4adc-4daa-aa12-769e3108abc8@csgroup.eu>
Hi Christophe,
> On 24. Feb 2025, at 13:56, Christophe Leroy wrote:
> Le 19/02/2025 à 12:20, Thorsten Blum a écrit :
>> Remove hard-coded strings by using the str_enabled_disabled() helper
>> function.
>> Use pr_debug() instead of printk(KERN_DEBUG) to silence a checkpatch
>> warning.
>> Reviewed-by: Ricardo B. Marlière <ricardo@marliere.net>
>> Signed-off-by: Thorsten Blum <thorsten.blum@linux.dev>
>> ---
>
> When you resend a patch, please tell why here (below the ---) so that we know the reason.
A "resend" is meant as a "ping" and the patch is always unmodified.
From [1]: "Don’t add “RESEND” when you are submitting a modified version
of your patch or patch series - “RESEND” only applies to resubmission of
a patch or patch series which have not been modified in any way from the
previous submission."
When a patch is not in -next yet or when it's been a week or longer and
I haven't received any feedback, I eventually follow up on it by
resending the same patch.
You're the first one to ask for a reason for resending.
> At the time being I have several duplicated patches from you and I don't know what to do with them which one to keep and which one to drop.
They're the same - feel free to pick the original patch or the resend.
Thanks,
Thorsten
[1] https://www.kernel.org/doc/html/latest/process/submitting-patches.html#don-t-get-discouraged-or-impatient
prev parent reply other threads:[~2025-02-24 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 11:20 [RESEND PATCH] powerpc: mpic: Use str_enabled_disabled() helper function Thorsten Blum
2025-02-24 12:56 ` Christophe Leroy
2025-02-24 14:09 ` Thorsten Blum [this message]
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=AE3E083C-D554-449B-9C67-81556D06FD35@linux.dev \
--to=thorsten.blum@linux.dev \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=ricardo@marliere.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.