Linux-BTRFS Archive on lore.kernel.org
 help / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH RESEND 1/2] btrfs-progs: check for no result before using results
Date: Sat, 2 Mar 2019 18:19:39 +0800
Message-ID: <0b5529a7-f8e3-9bff-6f4d-eb70c4b96d91@oracle.com> (raw)
In-Reply-To: <20190301164156.GT31119@twin.jikos.cz>



On 3/2/19 12:41 AM, David Sterba wrote:
> On Thu, Jan 31, 2019 at 06:05:40PM +0800, Anand Jain wrote:
>> User space understands the ioctl BTRFS_IOC_DEV_REPLACE command status
>> using the struct btrfs_ioctl_dev_replace_args::result, and so userspace
>> initializes this to BTRFS_IOCTL_DEV_REPLACE_RESULT_NO_RESULT, so exclude
>> this value in checking for the error.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> 
> 1 and 2 applied, thanks.
> 

Thanks.

  While at btrfs-progs you could include [1] as well.

[1]
  [PATCH v4] btrfs-progs: dump-tree: add noscan option
  https://patchwork.kernel.org/patch/10832585/

-Anand

  reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 10:05 Anand Jain
2019-01-31 10:05 ` [PATCH RESEND 2/2] btrfs-progs: replace: gracefully handle the exclusive operation report Anand Jain
2019-02-07 21:38 ` [PATCH RESEND 1/2] btrfs-progs: check for no result before using results Anand Jain
2019-03-01 16:41 ` David Sterba
2019-03-02 10:19   ` Anand Jain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-22 17:43 Anand Jain
2019-01-16  3:13 Anand Jain
2019-01-25 11:21 ` Anand Jain
2019-01-08  4:09 Anand Jain

Reply instructions:

You may reply publically 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=0b5529a7-f8e3-9bff-6f4d-eb70c4b96d91@oracle.com \
    --to=anand.jain@oracle.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

Linux-BTRFS Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-btrfs/0 linux-btrfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-btrfs linux-btrfs/ https://lore.kernel.org/linux-btrfs \
		linux-btrfs@vger.kernel.org linux-btrfs@archiver.kernel.org
	public-inbox-index linux-btrfs


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-btrfs


AGPL code for this site: git clone https://public-inbox.org/ public-inbox