Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, dsterba@suse.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 0/5] define BTRFS_DEV_STATE
Date: Wed, 13 Dec 2017 06:38:12 +0800	[thread overview]
Message-ID: <d37abb08-087f-7372-2196-c98b60229b63@oracle.com> (raw)
In-Reply-To: <20171212174249.GN3553@twin.jikos.cz>



On 12/13/2017 01:42 AM, David Sterba wrote:
> On Sun, Dec 10, 2017 at 05:15:17PM +0800, Anand Jain wrote:
>> As of now device properties and states are being represented as int
>> variable, patches here makes them bit flags instead. Further, wip
>> patches such as device failed state needs this cleanup.
>>
>> v2:
>>   Adds BTRFS_DEV_STATE_REPLACE_TGT
>>   Adds BTRFS_DEV_STATE_FLUSH_SENT
>>   Drops BTRFS_DEV_STATE_CAN_DISCARD
>>   Starts bit flag from the bit 0
>>   Drops unrelated change - declare btrfs_device
>>
>> v3:
>>   Fix static checker warning, define respective dev state as bit number
> 
> The define numbers are fixed but the whitespace changes that I made in
> misc-next

  Will do next time. Thanks. I don't see misc-next. Is it for-next ?

  git branch -a
* master
   remotes/origin/HEAD -> origin/master
   remotes/origin/for-4.13-part1
   remotes/origin/for-4.14
   remotes/origin/for-4.15-rc2
   remotes/origin/for-4.15-rc3
   remotes/origin/for-chris-4.12
   remotes/origin/for-next
   remotes/origin/for-next-test
   remotes/origin/master
   remotes/origin/nowait-aio-btrfs-fixup
git remote -v
origin	git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git (fetch)
origin	git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git (push)

Thanks, Anand


> while merging the patches are not in v3. I'd expect that you
> update your patches if there's another iteration and there have been
> changes to the merged ones, or send me only incrementals to the merged
> code or instructions how to fix it up if it's a trivial change like
> that.

  reply	other threads:[~2017-12-12 23:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10  9:15 [PATCH v3 0/5] define BTRFS_DEV_STATE Anand Jain
2017-12-10  9:15 ` [PATCH v3 1/5] btrfs: cleanup device states define BTRFS_DEV_STATE_WRITEABLE Anand Jain
2017-12-10  9:15 ` [PATCH v3 2/5] btrfs: cleanup device states define BTRFS_DEV_STATE_IN_FS_METADATA Anand Jain
2017-12-10  9:15 ` [PATCH v3 3/5] btrfs: cleanup device states define BTRFS_DEV_STATE_MISSING Anand Jain
2017-12-10  9:15 ` [PATCH v3 4/5] btrfs: cleanup device states define BTRFS_DEV_STATE_REPLACE_TGT Anand Jain
2017-12-10  9:15 ` [PATCH v3 5/5] btrfs: cleanup device states define BTRFS_DEV_STATE_FLUSH_SENT Anand Jain
2017-12-12 17:42 ` [PATCH v3 0/5] define BTRFS_DEV_STATE David Sterba
2017-12-12 22:38   ` Anand Jain [this message]
2017-12-13  2:26     ` David Sterba
2017-12-13  9:57       ` Timofey Titovets
2017-12-13 18:44         ` 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=d37abb08-087f-7372-2196-c98b60229b63@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --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