From: "Wei, Jiangang" <weijg.fnst@cn.fujitsu.com>
To: "famz@redhat.com" <famz@redhat.com>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
"mreitz@redhat.com" <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block/raw-posix: Fix error_report of mounting message
Date: Thu, 2 Jun 2016 03:04:20 +0000 [thread overview]
Message-ID: <1464836600.5185.7.camel@localhost> (raw)
In-Reply-To: <20160601072326.GF8639@ad.usersys.redhat.com>
On Wed, 2016-06-01 at 15:23 +0800, Fam Zheng wrote:
> On Wed, 06/01 15:08, Wei Jiangang wrote:
> > Use a single error_printf to replace triple error_report.
> >
> > Signed-off-by: Wei Jiangang <weijg.fnst@cn.fujitsu.com>
> > ---
> > block/raw-posix.c | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/block/raw-posix.c b/block/raw-posix.c
> > index a4f5a1b..141b01a 100644
> > --- a/block/raw-posix.c
> > +++ b/block/raw-posix.c
> > @@ -2061,11 +2061,11 @@ static bool setup_cdrom(char *bsd_path, Error **errp)
> > /* Prints directions on mounting and unmounting a device */
> > static void print_unmounting_directions(const char *file_name)
> > {
> > - error_report("If device %s is mounted on the desktop, unmount"
> > - " it first before using it in QEMU", file_name);
> > - error_report("Command to unmount device: diskutil unmountDisk %s",
> > - file_name);
> > - error_report("Command to mount device: diskutil mountDisk %s", file_name);
> > + error_printf("If device %s is mounted on the desktop, unmount"
> > + " it first before using it in QEMU\n"
> > + "Command to unmount device: diskutil unmountDisk %s\n"
> > + "Command to mount device: diskutil mountDisk %s\n",
> > + file_name, file_name, file_name);
>
> I'd say it's less readable with a worse alignment to the parameters.
Hi, Fam
Thanks for your comment.
You mean every error_report() followed by file_name is more readable ?
or my codes dosen't follow a good alignment format?
Wei
>
> Fam
>
>
next prev parent reply other threads:[~2016-06-02 3:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 7:08 [Qemu-devel] [PATCH] block/raw-posix: Fix error_report of mounting message Wei Jiangang
2016-06-01 7:23 ` Fam Zheng
2016-06-02 3:04 ` Wei, Jiangang [this message]
2016-06-02 3:15 ` Fam Zheng
2016-06-02 7:57 ` Markus Armbruster
2016-06-02 10:46 ` Wei, Jiangang
2016-06-03 9:00 ` Fam Zheng
2016-06-03 9:56 ` Wei, Jiangang
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=1464836600.5185.7.camel@localhost \
--to=weijg.fnst@cn.fujitsu.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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).