From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Joe Perches <joe@perches.com>
Cc: linuxppc-dev@lists.ozlabs.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] powerpc/powernv: Rename pe_level_printk to pe_printk and embed KERN_LEVEL in format
Date: Thu, 28 Aug 2025 06:50:59 +0200 [thread overview]
Message-ID: <4c7e5a00-87dd-4836-a57e-45282ddf4c0b@csgroup.eu> (raw)
In-Reply-To: <5b914354f29e58097e373dde76ee26b246a64ce6.camel@perches.com>
Le 28/08/2025 à 02:04, Joe Perches a écrit :
> [Vous ne recevez pas souvent de courriers de joe@perches.com. Découvrez pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification ]
>
> On Wed, 2025-08-27 at 18:42 +0200, Christophe Leroy wrote:
>> Hi Joe
>>
>> Le 21/06/2019 à 07:36, Joe Perches a écrit :
>>> Remove the separate KERN_<LEVEL> from each pe_level_printk and
>>> instead add the KERN_<LEVEL> to the format.
>
> Hello Christophe.
>
> It's over 6 years since I wrote that.
> Is that the typical review time? ;)
:)
I'm trying to clean patchwork and drop stale patches that are still
there. At the moment we have 240 'new' patches. 88 of them are older
than one year, with a few older ones being almost 10 years old.
>
> I would expect it doesn't apply anyway
> though it should make the object size
> a tiny bit smaller.
It still applies when doing a 3-way merge indeed.
Christophe
prev parent reply other threads:[~2025-08-28 5:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 5:36 [PATCH] powerpc/powernv: Rename pe_level_printk to pe_printk and embed KERN_LEVEL in format Joe Perches
2025-08-27 16:42 ` Christophe Leroy
2025-08-28 0:04 ` Joe Perches
2025-08-28 4:50 ` Christophe Leroy [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=4c7e5a00-87dd-4836-a57e-45282ddf4c0b@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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