From: Christoph Hellwig <hch@lst.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Sterba <dsterba@suse.cz>, Kees Cook <keescook@google.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: linux-next: build warning after merge of the btrfs-kdave tree
Date: Mon, 26 Nov 2018 08:56:11 +0100 [thread overview]
Message-ID: <20181126075611.GA799@lst.de> (raw)
In-Reply-To: <20181126110629.45969c51@canb.auug.org.au>
On Mon, Nov 26, 2018 at 11:06:29AM +1100, Stephen Rothwell wrote:
> Introduced by commit
>
> cf8cddd38bab3 ("btrfs: don't abuse REQ_OP_* flags for btrfs_map_block")
>
> exposed by my new use of -Wimplicit-fallthrough
>
> I am not sure why this has only turned up now (as opposed to earlier
> today).
It looks like something only in linux-next moved the code around a bit.
Either way the fallthough looks fine, it will just need a little
/*FALLTHRU*/ annotation.
next prev parent reply other threads:[~2018-11-26 7:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 0:06 linux-next: build warning after merge of the btrfs-kdave tree Stephen Rothwell
2018-11-26 7:56 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-03 0:21 Stephen Rothwell
2019-05-03 13:37 ` David Sterba
2019-01-23 22:53 Stephen Rothwell
2019-01-28 16:53 ` David Sterba
2017-12-19 22:20 Stephen Rothwell
2017-12-20 0:12 ` Qu Wenruo
2017-12-21 16:49 ` David Sterba
2017-12-22 0:32 ` Qu Wenruo
2017-05-17 23:41 Stephen Rothwell
2017-05-18 12:50 ` David Sterba
2017-05-25 1:31 ` Stephen Rothwell
2016-11-28 0:02 Stephen Rothwell
2016-12-06 22:38 ` Stephen Rothwell
2016-12-14 15:19 ` David Sterba
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=20181126075611.GA799@lst.de \
--to=hch@lst.de \
--cc=dsterba@suse.cz \
--cc=keescook@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).