[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251125105218.4a1e02ad@gandalf.local.home>
Date: Tue, 25 Nov 2025 10:52:18 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Shrikanth Hegde <sshegde@...ux.ibm.com>
Cc: Greg KH <gregkh@...uxfoundation.org>, 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 Tue, 25 Nov 2025 08:19:45 +0530
Shrikanth Hegde <sshegde@...ux.ibm.com> wrote:
> > [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
> >
>
> I can follow this.
>
> PS: I was skeptical after last series mistake.
You may also want remove the [ ] and use '--' instead:
[PATCH 16/17] -- DO NOT APPLY!!! -- sysfs: Provide write method for paravirt
Because if someone were to do a b4 pull it would strip out the text within
the brackets. Using -- DO NOT APPLY!!! -- instead, would keep it in the
commit message. And then seeing that in the shortlog would be a really big
red flag ;-)
-- Steve
PS. I plan on changing my usages to use '--' instead of '[' ']'
Powered by blists - more mailing lists