From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: bo.li.liu@oracle.com
Subject: [PATCH 0/4] define BTRFS_DEV_STATE
Date: Wed, 29 Nov 2017 12:45:32 +0800 [thread overview]
Message-ID: <20171129044536.16260-1-anand.jain@oracle.com> (raw)
As of now device properties and states are being represented as int
variable. Patches in the ML such as device failed state needs this
cleanup as well.
Anand Jain (4):
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_CAN_DISCARD
fs/btrfs/dev-replace.c | 3 +-
fs/btrfs/disk-io.c | 23 ++++++---
fs/btrfs/extent-tree.c | 5 +-
fs/btrfs/extent_io.c | 3 +-
fs/btrfs/ioctl.c | 2 +-
fs/btrfs/scrub.c | 13 +++--
fs/btrfs/super.c | 7 +--
fs/btrfs/volumes.c | 129 ++++++++++++++++++++++++++++---------------------
fs/btrfs/volumes.h | 10 ++--
9 files changed, 118 insertions(+), 77 deletions(-)
--
2.15.0
next reply other threads:[~2017-11-29 4:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 4:45 Anand Jain [this message]
2017-11-29 4:45 ` [PATCH 1/4] btrfs: cleanup device states define BTRFS_DEV_STATE_WRITEABLE Anand Jain
2017-11-29 9:14 ` Nikolay Borisov
2017-11-29 9:59 ` Anand Jain
2017-11-29 4:45 ` [PATCH 2/4] btrfs: cleanup device states define BTRFS_DEV_STATE_IN_FS_METADATA Anand Jain
2017-11-29 9:20 ` Nikolay Borisov
2017-11-29 4:45 ` [PATCH 3/4] btrfs: cleanup device states define BTRFS_DEV_STATE_MISSING Anand Jain
2017-11-29 9:35 ` Nikolay Borisov
2017-11-29 4:45 ` [PATCH 4/4] btrfs: cleanup device states define BTRFS_DEV_STATE_CAN_DISCARD Anand Jain
2017-11-29 9:39 ` Nikolay Borisov
2017-11-29 10:55 ` 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=20171129044536.16260-1-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=bo.li.liu@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).