From: Paul Mackerras <paulus@ozlabs.org>
To: Joe Perches <joe@perches.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
kvm-ppc@vger.kernel.org
Subject: Re: [PATCH -next 016/491] KERNEL VIRTUAL MACHINE FOR POWERPC (KVM/powerpc): Use fallthrough;
Date: Fri, 20 Mar 2020 10:33:30 +1100 [thread overview]
Message-ID: <20200319233330.GE3260@blackberry> (raw)
In-Reply-To: <7584d7937f4bb929beb0b9f5e80523653297676d.camel@perches.com>
On Wed, Mar 18, 2020 at 06:22:29PM -0700, Joe Perches wrote:
> On Thu, 2020-03-19 at 12:18 +1100, Paul Mackerras wrote:
> > On Tue, Mar 10, 2020 at 09:51:30PM -0700, Joe Perches wrote:
> > > Convert the various uses of fallthrough comments to fallthrough;
> > >
> > > Done via script
> > > Link: https://lore.kernel.org/lkml/b56602fcf79f849e733e7b521bb0e17895d390fa.1582230379.git.joe.com/
> > >
> > > Signed-off-by: Joe Perches <joe@perches.com>
> >
> > The subject line should look like "KVM: PPC: Use fallthrough".
>
> There's no way to generate a subject line like that via a script
> so far as I can tell.
>
> > Apart from that,
> >
> > Acked-by: Paul Mackerras <paulus@ozlabs.org>
> >
> > How are these patches going upstream? Do you want me to take this via
> > my tree?
>
> If you want.
>
> Ideally, these changes would go in treewide via a script run
> by Linus at an -rc1, but if the change is OK with you, it'd
> be fine to have you apply it now.
I have taken this patch in my kvm-ppc-next branch.
Thanks,
Paul.
next prev parent reply other threads:[~2020-03-19 23:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 4:51 [PATCH -next 000/491] treewide: use fallthrough; Joe Perches
2020-03-11 4:51 ` [PATCH -next 016/491] KERNEL VIRTUAL MACHINE FOR POWERPC (KVM/powerpc): Use fallthrough; Joe Perches
2020-03-19 1:18 ` Paul Mackerras
2020-03-19 1:22 ` Joe Perches
2020-03-19 23:33 ` Paul Mackerras [this message]
2020-03-11 4:51 ` [PATCH -next 017/491] CELL BROADBAND ENGINE ARCHITECTURE: " Joe Perches
2020-03-11 8:08 ` Arnd Bergmann
2020-03-26 12:06 ` Michael Ellerman
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=20200319233330.GE3260@blackberry \
--to=paulus@ozlabs.org \
--cc=joe@perches.com \
--cc=kvm-ppc@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).