qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-trivial@nongnu.org, hangaohuai@huawei.com,
	peter.huangpeng@huawei.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC 5/5] savevm: Replace error_report() & error_free() with error_report_err()
Date: Tue, 3 Mar 2015 17:34:18 +0800	[thread overview]
Message-ID: <54F5801A.2090109@huawei.com> (raw)
In-Reply-To: <87sidm780f.fsf@blackfin.pond.sub.org>

On 2015/3/3 17:19, Markus Armbruster wrote:
> zhanghailiang <zhang.zhanghailiang@huawei.com> writes:
>
>> On 2015/3/2 18:26, Markus Armbruster wrote:
>>> zhanghailiang <zhang.zhanghailiang@huawei.com> writes:
>>>
>>>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>>>> ---
>>>>    savevm.c | 3 +--
>>>>    1 file changed, 1 insertion(+), 2 deletions(-)
>>>>
>>>> diff --git a/savevm.c b/savevm.c
>>>> index ce2b6a2..c4f8c39 100644
>>>> --- a/savevm.c
>>>> +++ b/savevm.c
>>>> @@ -932,8 +932,7 @@ int qemu_loadvm_state(QEMUFile *f)
>>>>        int ret;
>>>>
>>>>        if (qemu_savevm_state_blocked(&local_err)) {
>>>> -        error_report("%s", error_get_pretty(local_err));
>>>> -        error_free(local_err);
>>>> +        error_report_err(local_err);
>>>>            return -EINVAL;
>>>>        }
>>>
>>> This one's good.  My commit 565f65d "error: Use error_report_err() where
>>> appropriate" cleaned up this pattern, but a few more instances have
>>> since crept in, and this is one.
>>>
>>> I can see another one in hw/arm/virt.c machvirt_init().
>>>
>>>
>>
>> Er, do you mean the follow place ?
>>
>>         /* Handle any CPU options specified by the user */
>>          cc->parse_features(CPU(cpuobj), cpustr[1], &err);
>>          if (err) {
>>              error_report("%s", error_get_pretty(err));
>>              exit(1);
>>          }
>
> Yes.

OK, i will send a patch fix these two places. Thanks. :)

  reply	other threads:[~2015-03-03  9:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-28  9:05 [Qemu-devel] [PATCH RFC 0/5] Another patchset try to clean up around qerror_report_err() zhanghailiang
2015-02-28  9:05 ` [Qemu-devel] [PATCH RFC 1/5] serial-pci: Avoid qerror_report_err() outside QMP command handlers zhanghailiang
2015-03-02 10:02   ` Markus Armbruster
2015-02-28  9:05 ` [Qemu-devel] [PATCH RFC 2/5] qdev: " zhanghailiang
2015-03-02 10:11   ` Markus Armbruster
2015-02-28  9:05 ` [Qemu-devel] [PATCH RFC 3/5] pci-hotplug-old: " zhanghailiang
2015-03-02 10:12   ` Markus Armbruster
2015-02-28  9:05 ` [Qemu-devel] [PATCH RFC 4/5] pci-assign: " zhanghailiang
2015-03-02 10:14   ` Markus Armbruster
2015-02-28  9:05 ` [Qemu-devel] [PATCH RFC 5/5] savevm: Replace error_report() & error_free() with error_report_err() zhanghailiang
2015-03-02 10:26   ` Markus Armbruster
2015-03-03  6:11     ` zhanghailiang
2015-03-03  9:19       ` Markus Armbruster
2015-03-03  9:34         ` zhanghailiang [this message]
2015-03-02 10:01 ` [Qemu-devel] [PATCH RFC 0/5] Another patchset try to clean up around qerror_report_err() Markus Armbruster
2015-03-03  6:08   ` zhanghailiang

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=54F5801A.2090109@huawei.com \
    --to=zhang.zhanghailiang@huawei.com \
    --cc=armbru@redhat.com \
    --cc=hangaohuai@huawei.com \
    --cc=peter.huangpeng@huawei.com \
    --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).