From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/4] Add Error **errp for xen_host_pci_device_get()
Date: Tue, 5 Jan 2016 20:41:26 +0800 [thread overview]
Message-ID: <568BB9F6.9050309@cn.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1601051033210.31111@kaball.uk.xensource.com>
On 01/05/2016 06:40 PM, Stefano Stabellini wrote:
> On Tue, 5 Jan 2016, Cao jin wrote:
[...]
>
> This is true, however I think that relying on it is error prone: in a
> couple of years from now somebody might change the call sequence without
> updating the error handling (easy to forget), causing QEMU to crash on
> error. I think it is safer not to rely on errp != NULL.
>
I see, sounds reasonable
>
[...]
> I think we only need to use a local Error variable when we want to check
> for the returned error, in cases such as:
>
> if (*errp) {
>
> In other cases, when we are not interested in *errp, we can simply
> propagate the error, like you have done in your patches.
>
Ok, will fix it
> .
>
--
Yours Sincerely,
Cao Jin
next prev parent reply other threads:[~2016-01-05 12:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-27 13:40 [Qemu-devel] [PATCH v2 0/4] Convert to realize() Cao jin
2015-12-27 13:40 ` [Qemu-devel] [PATCH v2 1/4] Add Error **errp for xen_host_pci_device_get() Cao jin
2016-01-04 15:15 ` Stefano Stabellini
2016-01-05 5:31 ` Cao jin
2016-01-05 7:23 ` Cao jin
2016-01-05 10:40 ` Stefano Stabellini
2016-01-05 12:41 ` Cao jin [this message]
2015-12-27 13:40 ` [Qemu-devel] [PATCH v2 2/4] Add Error **errp for xen_pt_setup_vga() Cao jin
2016-01-04 15:18 ` Stefano Stabellini
2015-12-27 13:40 ` [Qemu-devel] [PATCH v2 3/4] Add Error **errp for xen_pt_config_init() Cao jin
2016-01-04 15:23 ` Stefano Stabellini
2015-12-27 13:40 ` [Qemu-devel] [PATCH v2 4/4] Xen PCI passthru: convert to realize() Cao jin
2016-01-04 15:29 ` Stefano Stabellini
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=568BB9F6.9050309@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.