From: Chao Yu <yuchao0@huawei.com>
To: Surbhi Palande <f2fsnewbie@gmail.com>,
<linux-f2fs-devel@lists.sourceforge.net>
Cc: Surbhi Palande <csurbhi@gmail.com>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Damien Le Moal <damien.lemoal@wdc.com>
Subject: Re: [f2fs-dev] [f2fs-tools][PATCH] libf2fs: Throw an error when zone dev info not found
Date: Fri, 2 Aug 2019 11:42:25 +0800 [thread overview]
Message-ID: <0832e6dd-1b38-2b50-4e8a-3db6a1af41c9@huawei.com> (raw)
In-Reply-To: <20190802024748.17987-1-f2fsnewbie@gmail.com>
On 2019/8/2 10:47, Surbhi Palande wrote:
> From: Surbhi Palande <csurbhi@gmail.com>
>
> When the -m option is specified to format a Zoned device,
> do not fall back to the non-zoned mode in case information
> about the device is not found.
>
> Explicitly specify this error to the user.
>
> Signed-off-by: Surbhi Palande <csurbhi@gmail.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-08-02 3:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 1:26 [f2fs-dev] [f2fs-tools][PATCH] Throw an error when zone device info not found Surbhi Palande
2019-08-01 1:47 ` Chao Yu
2019-08-01 2:56 ` Damien Le Moal
2019-08-02 2:47 ` [f2fs-dev] [f2fs-tools][PATCH] libf2fs: Throw an error when zone dev " Surbhi Palande
2019-08-02 3:19 ` Damien Le Moal
2019-08-02 3:42 ` Chao Yu [this message]
[not found] ` <CAMBkX3cF9aQ28rJ2XYZRjfyYXNWBREmc9nZqgqMtimM2eHsEXQ@mail.gmail.com>
2019-08-02 3:32 ` [f2fs-dev] [f2fs-tools][PATCH] Throw an error when zone device " Damien Le Moal
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=0832e6dd-1b38-2b50-4e8a-3db6a1af41c9@huawei.com \
--to=yuchao0@huawei.com \
--cc=csurbhi@gmail.com \
--cc=damien.lemoal@wdc.com \
--cc=f2fsnewbie@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).