From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-btrfs@vger.kernel.org,
josef@toxicpanda.com, dsterba@suse.com
Subject: Re: [PATCH v5 2/5] btrfs: create read policy framework
Date: Wed, 19 Feb 2020 13:35:54 +0100 [thread overview]
Message-ID: <20200219123554.GW2902@suse.cz> (raw)
In-Reply-To: <c06da00e-2cb2-806a-f441-6d5a29c7293c@oracle.com>
On Wed, Feb 19, 2020 at 07:40:47PM +0800, Anand Jain wrote:
>
> > In file included from fs/btrfs/volumes.c:18:0:
> > fs/btrfs/volumes.c: In function 'find_live_mirror':
>
> >>> fs/btrfs/ctree.h:3143:4: warning: this statement may fall through [-Wimplicit-fallthrough=]
>
> This is not a bug. May be we can make the robot happy.
Since 5.5 all fall-trhough switch labels should be annotated properly.
next prev parent reply other threads:[~2020-02-19 12:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 11:12 [PATCH v5 0/5] readmirror feature (sysfs and in-memory only approach; with new read_policy device) Anand Jain
2020-02-17 11:12 ` [PATCH v5 1/5] btrfs: add btrfs_strmatch helper Anand Jain
2020-02-17 11:12 ` [PATCH v5 2/5] btrfs: create read policy framework Anand Jain
2020-02-19 7:41 ` kbuild test robot
2020-02-19 11:40 ` Anand Jain
2020-02-19 12:35 ` David Sterba [this message]
2020-02-17 11:12 ` [PATCH v5 3/5] btrfs: create read policy sysfs attribute, pid Anand Jain
2020-02-17 11:12 ` [PATCH v5 4/5] btrfs: introduce new device-state read_preferred Anand Jain
2020-02-17 11:12 ` [PATCH v5 5/5] btrfs: introduce new read_policy device Anand Jain
2020-02-18 16:35 ` [PATCH v5 0/5] readmirror feature (sysfs and in-memory only approach; with new read_policy device) David Sterba
2020-02-19 11:42 ` Anand Jain
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=20200219123554.GW2902@suse.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lkp@intel.com \
/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).