qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, Aakriti Gupta <aakritty@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2] convert fprintf() calls to error_setg() in block/qed.c:bdrv_qed_create()
Date: Tue, 18 Mar 2014 10:44:55 +0100	[thread overview]
Message-ID: <20140318094455.GH4607@noname.str.redhat.com> (raw)
In-Reply-To: <20140317145948.GG4888@stefanha-thinkpad.redhat.com>

Am 17.03.2014 um 15:59 hat Stefan Hajnoczi geschrieben:
> On Sat, Mar 15, 2014 at 03:05:23PM +0530, Aakriti Gupta wrote:
> > This patch converts fprintf() calls to error_setg() in block/qed.c:bdrv_qed_create()
> > (error_setg() is part of error reporting API in include/qapi/error.h)
> > 
> > Signed-off-by: Aakriti Gupta <aakritty@gmail.com>
> > ---
> >  block/qed.c |    8 ++++----
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> Acked-by: Stefan Hajnoczi <stefanha@redhat.com>

Thanks, applied to the block-next branch for qemu 2.1.

> >      if (!qed_is_cluster_size_valid(cluster_size)) {
> > -        fprintf(stderr, "QED cluster size must be within range [%u, %u] and power of 2\n",
> > +        error_setg(errp, "QED cluster size must be within range [%u, %u] and power of 2",
> >                  QED_MIN_CLUSTER_SIZE, QED_MAX_CLUSTER_SIZE);
> 
> Kevin: Do you want to fix up the indentation of the next line when
> merging?

Sure, I did that, and wrapped the line at 80 characters, too.

Kevin

      reply	other threads:[~2014-03-18  9:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-15  9:35 [Qemu-devel] [PATCH v2] convert fprintf() calls to error_setg() in block/qed.c:bdrv_qed_create() Aakriti Gupta
2014-03-17 14:59 ` Stefan Hajnoczi
2014-03-18  9:44   ` Kevin Wolf [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=20140318094455.GH4607@noname.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=aakritty@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).