[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251125110848.2230156b@gandalf.local.home>
Date: Tue, 25 Nov 2025 11:08:48 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc: Shrikanth Hegde <sshegde@...ux.ibm.com>, 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 11:02:38 -0500
Konstantin Ryabitsev <konstantin@...uxfoundation.org> wrote:
> Small correction -- it's git itself that strips all content inside [], not b4
> specifically.
Yes of course. Sorry, I didn't want to blame b4. I actually download the
patch series from patchwork and then do git am which does the stripping. I
just wanted to state a more common workflow, which is usually b4 followed
by a blind execution of git am. Where it does the stripping isn't of
importance at that point.
-- Steve
Powered by blists - more mailing lists