[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251124122459.00e86457@gandalf.local.home>
Date: Mon, 24 Nov 2025 12:24:59 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Shrikanth Hegde <sshegde@...ux.ibm.com>, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, mingo@...hat.com, peterz@...radead.org,
juri.lelli@...hat.com, vincent.guittot@...aro.org, tglx@...utronix.de,
yury.norov@...il.com, maddy@...ux.ibm.com, srikar@...ux.ibm.com,
pbonzini@...hat.com, seanjc@...gle.com, kprateek.nayak@....com,
vschneid@...hat.com, iii@...ux.ibm.com, huschle@...ux.ibm.com,
dietmar.eggemann@....com, christophe.leroy@...roup.eu
Subject: Re: [PATCH 16/17] sysfs: Provide write method for paravirt
On Mon, 24 Nov 2025 18:04:48 +0100
Greg KH <gregkh@...uxfoundation.org> wrote:
> As you added this to this series, if it is picked up, it WILL be merged
> :(
>
> Please try a "Nacked-by:" or something else to keep patches from being
> applied. Or better yet, send them as a totally separate series.
Agreed. But when I do this to a patch in a series, I usually add in subject:
[PATCH 16/17][DO NOT APPLY!!!] sysfs: Provide write method for paravirt
in order to make it stand out, and not a footnote after the tags.
-- Steve
Powered by blists - more mailing lists