From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: qemu-devel@nongnu.org
Cc: lersek@redhat.com, lcapitulino@redhat.com, luonengjun@huawei.com,
peter.huangpeng@huawei.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 0/2] dump: let dump_error return error reason to caller
Date: Sun, 28 Sep 2014 09:18:50 +0800 [thread overview]
Message-ID: <542761FA.9070704@huawei.com> (raw)
In-Reply-To: <542212C1.9050908@huawei.com>
Hi,
Ping^2...
Can anyone help reviewing this patch? Luiz? Eric? Markus? Thanks;)
Best regards,
zhanghailiang
On 2014/9/24 8:39, zhanghailiang wrote:
> Hi,
>
> Ping...
>
> Thanks,
> zhanghailiang
>
> On 2014/9/19 14:43, zhanghailiang wrote:
>> Hi,
>>
>> In original code, Function dump_error ignores its second parameter which contains
>> error reason, it is better to return the error message to the caller.
>>
>> Here we use error_setg to return the error info to caller.
>> And at the same time, we turn functions like write_elf64_note() to void,
>> Because functions shouldn't return an error code _and_ an Error object.
>> After this modification the code will be more clean.
>>
>> v5 -> v6
>> - Don't check *errp directly, if errp is NULL, there will be an error,
>> Instead, check a local variable *local_err (Markus Armbruster)
>> v4 -> v5:
>> - Turn functions like write_elf64_note() to void (Luiz Capitulino)
>> v3 -> v4:
>> - Adjust the errp argument to the end
>> - Remove trailing '.' in error messages
>> v2 -> v3:
>> - Drop the '\n' in the message when call dump_error(Eric Blake)
>> v1 -> v2:
>> - Return the error reason to the caller (Luiz Capitulino)
>>
>> zhanghailiang (2):
>> dump: let dump_error return error info to caller
>> dump: Don't return error code when return an Error object
>>
>> dump.c | 382 +++++++++++++++++++++++++++++++----------------------------------
>> 1 file changed, 182 insertions(+), 200 deletions(-)
>>
>
>
>
>
>
prev parent reply other threads:[~2014-09-28 1:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 6:43 [Qemu-devel] [PATCH v6 0/2] dump: let dump_error return error reason to caller zhanghailiang
2014-09-19 6:43 ` [Qemu-devel] [PATCH v6 1/2] dump: let dump_error return error info " zhanghailiang
2014-09-29 7:48 ` Markus Armbruster
2014-09-29 8:06 ` zhanghailiang
2014-09-19 6:43 ` [Qemu-devel] [PATCH v6 2/2] dump: Don't return error code when return an Error object zhanghailiang
2014-09-29 8:06 ` Markus Armbruster
2014-09-30 8:39 ` zhanghailiang
2014-09-24 0:39 ` [Qemu-devel] [PATCH v6 0/2] dump: let dump_error return error reason to caller zhanghailiang
2014-09-28 1:18 ` zhanghailiang [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=542761FA.9070704@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=lersek@redhat.com \
--cc=luonengjun@huawei.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@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).