From: Anand Jain <anand.jain@oracle.com>
To: Su Yue <Damenly_Su@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v4] btrfs-progs: dump-tree: add noscan option
Date: Mon, 11 Mar 2019 21:49:06 +0800 [thread overview]
Message-ID: <23ab3e25-b285-e445-0fce-18607d25d972@oracle.com> (raw)
In-Reply-To: <aab9c700-bb80-9481-3fd6-151872107612@gmx.com>
>> + if (ret) {
>> + error("device scan %s: %s", argv[dev_optind],
>> + strerror(-ret));
>
> Nit:
>
> Should do some change to follow current "%m" style?
>
> Thanks
> Su
Ok will change it. Thanks for catching.
Thanks, Anand
prev parent reply other threads:[~2019-03-11 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 6:54 [PATCH v4] btrfs-progs: dump-tree: add noscan option Anand Jain
2019-03-11 10:11 ` Nikolay Borisov
2019-03-11 14:44 ` Anand Jain
2019-03-11 15:19 ` Nikolay Borisov
2019-03-11 12:33 ` Su Yue
2019-03-11 13:49 ` Anand Jain [this message]
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=23ab3e25-b285-e445-0fce-18607d25d972@oracle.com \
--to=anand.jain@oracle.com \
--cc=Damenly_Su@gmx.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).