From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 0/5] define BTRFS_DEV_STATE
Date: Mon, 4 Dec 2017 21:28:42 +0100 [thread overview]
Message-ID: <20171204202842.GB3553@twin.jikos.cz> (raw)
In-Reply-To: <20171204045456.8602-1-anand.jain@oracle.com>
On Mon, Dec 04, 2017 at 12:54:51PM +0800, Anand Jain wrote:
> As of now device properties and states are being represented as int
> variable. So clean that up using bitwise operations. Also patches in
> the ML such as device failed state needs this cleanup as well.
>
> V2:
> Accepts all comments from Nikolay.
> Drops can_discard.
> Adds BTRFS_DEV_STATE_REPLACE_TGT and BTRFS_DEV_STATE_FLUSH_SENT
> patches.
>
> Anand Jain (5):
> btrfs: cleanup device states define BTRFS_DEV_STATE_WRITEABLE
> btrfs: cleanup device states define BTRFS_DEV_STATE_IN_FS_METADATA
> btrfs: cleanup device states define BTRFS_DEV_STATE_MISSING
> btrfs: cleanup device states define BTRFS_DEV_STATE_REPLACE_TGT
> btrfs: cleanup device states define BTRFS_DEV_STATE_FLUSH_SENT
1-5 added to next. I had to tweak the whitespace in the conditions.
next prev parent reply other threads:[~2017-12-04 20:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 4:54 [PATCH v2 0/5] define BTRFS_DEV_STATE Anand Jain
2017-12-04 4:54 ` [PATCH v2 1/5] btrfs: cleanup device states define BTRFS_DEV_STATE_WRITEABLE Anand Jain
2017-12-04 4:54 ` [PATCH v2 2/5] btrfs: cleanup device states define BTRFS_DEV_STATE_IN_FS_METADATA Anand Jain
2017-12-04 4:54 ` [PATCH v2 3/5] btrfs: cleanup device states define BTRFS_DEV_STATE_MISSING Anand Jain
2017-12-04 4:54 ` [PATCH v2 4/5] btrfs: cleanup device states define BTRFS_DEV_STATE_REPLACE_TGT Anand Jain
2017-12-04 4:54 ` [PATCH v2 5/5] btrfs: cleanup device states define BTRFS_DEV_STATE_FLUSH_SENT Anand Jain
2017-12-04 20:28 ` David Sterba [this message]
2017-12-05 1:20 ` [PATCH v2 0/5] define BTRFS_DEV_STATE Anand Jain
2017-12-05 13:07 ` David Sterba
2017-12-05 21:24 ` 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=20171204202842.GB3553@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).