[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <AE3E083C-D554-449B-9C67-81556D06FD35@linux.dev>
Date: Mon, 24 Feb 2025 15:09:19 +0100
From: Thorsten Blum <thorsten.blum@...ux.dev>
To: Christophe Leroy <christophe.leroy@...roup.eu>
Cc: Madhavan Srinivasan <maddy@...ux.ibm.com>,
Michael Ellerman <mpe@...erman.id.au>,
Nicholas Piggin <npiggin@...il.com>,
Naveen N Rao <naveen@...nel.org>,
"Ricardo B. Marlière" <ricardo@...liere.net>,
linuxppc-dev@...ts.ozlabs.org,
linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH] powerpc: mpic: Use str_enabled_disabled() helper
function
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@...liere.net>
>> Signed-off-by: Thorsten Blum <thorsten.blum@...ux.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
Powered by blists - more mailing lists