From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Kees Cook <keescook@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] lib/siphash.c: mark expected switch fall-throughs
Date: Fri, 26 Apr 2019 06:28:53 +1000 [thread overview]
Message-ID: <20190426062844.09ae86e2@canb.auug.org.au> (raw)
In-Reply-To: <20190425174615.GA8544@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
Hi Greg,
On Thu, 25 Apr 2019 19:46:15 +0200 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Apr 16, 2019 at 06:03:58PM +0900, Jason A. Donenfeld wrote:
> > On Tue, Apr 16, 2019 at 4:27 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> > > where we are expecting to fall through.
> > >
> > > This patch aims to suppress up to 18 missing-break-in-switch false
> > > positives on some architectures.
> > >
> > > Cc: Jason A. Donenfeld <Jason@zx2c4.com>
> > > Cc: Gustavo A. R. Silva <gustavo@embeddedor.com>
> > > Cc: Kees Cook <keescook@chromium.org>
> > > Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> >
> > Looks good to me, thanks for this.
> >
> > Reviewed-by: Jason A. Donenfeld <Jason@zx2c4.com>
> >
> > Perhaps Greg can take it through his tree?
>
> Me? Ok, fine, I'll go queue it up...
Excellent, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-04-25 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 7:27 Stephen Rothwell
2019-04-16 9:03 ` Jason A. Donenfeld
2019-04-25 17:46 ` Greg Kroah-Hartman
2019-04-25 18:03 ` Gustavo A. R. Silva
2019-04-25 20:28 ` Stephen Rothwell [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=20190426062844.09ae86e2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Jason@zx2c4.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo@embeddedor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®