From: Stefan Hajnoczi <stefanha@gmail.com>
To: Vikhyat Umrao <vumrao@redhat.com>
Cc: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] rbd:change error_setg() to error_setg_errno()
Date: Fri, 6 May 2016 17:29:55 +0100 [thread overview]
Message-ID: <20160506162955.GD23075@stefanha-x1.localdomain> (raw)
In-Reply-To: <CACkKZgcbPBLqLHAg+uWXoiuUBj=+ZEMqRrTk9bfw9nAtKEa8uA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2414 bytes --]
On Fri, May 06, 2016 at 10:44:41AM +0530, Vikhyat Umrao wrote:
> On Fri, May 6, 2016 at 6:14 AM, Fam Zheng <famz@redhat.com> wrote:
>
> > On Thu, 05/05 15:06, Jeff Cody wrote:
> > > On Thu, May 05, 2016 at 06:45:15PM +0100, Stefan Hajnoczi wrote:
> > > > On Mon, May 02, 2016 at 09:55:17PM +0530, Vikhyat Umrao wrote:
> > > > > From 1c63c246f47a1a65d8740d7ce3725fe3820c0a37 Mon Sep 17 00:00:00
> > 2001
> > > > > From: Vikhyat Umrao <vumrao@redhat.com>
> > > > > Date: Mon, 2 May 2016 21:47:31 +0530
> > > > > Subject: [PATCH] rbd:change error_setg() to error_setg_errno()
> > > > >
> > > > > Ceph RBD block driver does not use error_setg_errno() where
> > > > > it is possible to use. This patch replaces error_setg()
> > > > > from error_setg_errno().
> > > > >
> > > > > Signed-off-by: Vikhyat Umrao <vumrao@redhat.com>
> > > > > ---
> > > > > block/rbd.c | 37 ++++++++++++++++++++++---------------
> > > > > 1 file changed, 22 insertions(+), 15 deletions(-)
> > > > >
> > > > > diff --git a/block/rbd.c b/block/rbd.c
> > > > > index 5bc5b32..c286b32 100644
> > > > > --- a/block/rbd.c
> > > > > +++ b/block/rbd.c
> > > > > @@ -290,7 +290,7 @@ static int qemu_rbd_set_conf(rados_t cluster,
> > const
> > > > > char *conf,
> > > > > if (only_read_conf_file) {
> > > > > ret = rados_conf_read_file(cluster, value);
> > > > > if (ret < 0) {
> > > > > - error_setg(errp, "error reading conf file %s",
> > value);
> > > > > + error_setg_errno(errp, -ret, "error reading
> > conf file
> > > > > %s", value);
> > > >
> > > > Please use scripts/checkpatch.pl to scan patches for coding style
> > > > violations. This line exceeds the maximum line length.
> > >
> > >
> > > Also, if you can use something like git send-email, it formats the patch
> > > emails much nicer -- which makes it easier to review & apply.
> >
> > Also please use ./scripts/get_maintainer.pl to get a more complete
> > recipient
> > list (for example it will report qemu-block@nongnu.org and other block
> > layer maintainers).
> >
> > Fam
> >
>
> Thank you everyone for your inputs. Sure I will fix the current patch and
> will check it with given scripts and then will send patch v2.
This page has the guidelines for submitting patches:
http://qemu-project.org/Contribute/SubmitAPatch
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-05-06 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 16:25 [Qemu-devel] [PATCH] rbd:change error_setg() to error_setg_errno() Vikhyat Umrao
2016-05-05 17:45 ` Stefan Hajnoczi
2016-05-05 19:06 ` Jeff Cody
2016-05-06 0:44 ` Fam Zheng
2016-05-06 5:14 ` Vikhyat Umrao
2016-05-06 16:29 ` Stefan Hajnoczi [this message]
2016-05-09 7:56 ` Vikhyat Umrao
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=20160506162955.GD23075@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vumrao@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).