All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: Markus Armbruster <armbru@redhat.com>, Eric Blake <eblake@redhat.com>
Cc: qemu-trivial@nongnu.org, hangaohuai@huawei.com,
	peter.huangpeng@huawei.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] error: Replace error_report() & error_free() with error_report_err()
Date: Wed, 4 Mar 2015 16:53:58 +0800	[thread overview]
Message-ID: <54F6C826.1010209@huawei.com> (raw)
In-Reply-To: <874mq144ks.fsf@blackfin.pond.sub.org>

On 2015/3/4 15:14, Markus Armbruster wrote:
> Eric Blake <eblake@redhat.com> writes:
>
>> On 03/03/2015 02:55 AM, zhanghailiang wrote:
>>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>>> ---
>>
>> Might have been nice to mention this was a continuation of the work
>> started in commit 565f65d27.
>
> Yes.  Perhaps the -trivial maintainer can stick in a reference on
> commit.
>

:), i will send v2, to make his life easy. Thanks.

>>>   hw/arm/virt.c | 2 +-
>>>   savevm.c      | 3 +--
>>>   2 files changed, 2 insertions(+), 3 deletions(-)
>>
>> Reviewed-by: Eric Blake <eblake@redhat.com>
>
>




WARNING: multiple messages have this Message-ID (diff)
From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: Markus Armbruster <armbru@redhat.com>, Eric Blake <eblake@redhat.com>
Cc: qemu-trivial@nongnu.org, hangaohuai@huawei.com,
	peter.huangpeng@huawei.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] error: Replace error_report() & error_free() with error_report_err()
Date: Wed, 4 Mar 2015 16:53:58 +0800	[thread overview]
Message-ID: <54F6C826.1010209@huawei.com> (raw)
In-Reply-To: <874mq144ks.fsf@blackfin.pond.sub.org>

On 2015/3/4 15:14, Markus Armbruster wrote:
> Eric Blake <eblake@redhat.com> writes:
>
>> On 03/03/2015 02:55 AM, zhanghailiang wrote:
>>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>>> ---
>>
>> Might have been nice to mention this was a continuation of the work
>> started in commit 565f65d27.
>
> Yes.  Perhaps the -trivial maintainer can stick in a reference on
> commit.
>

:), i will send v2, to make his life easy. Thanks.

>>>   hw/arm/virt.c | 2 +-
>>>   savevm.c      | 3 +--
>>>   2 files changed, 2 insertions(+), 3 deletions(-)
>>
>> Reviewed-by: Eric Blake <eblake@redhat.com>
>
>

  reply	other threads:[~2015-03-04  8:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  9:55 [Qemu-trivial] [PATCH] error: Replace error_report() & error_free() with error_report_err() zhanghailiang
2015-03-03  9:55 ` [Qemu-devel] " zhanghailiang
2015-03-03 17:18 ` [Qemu-trivial] " Eric Blake
2015-03-03 17:18   ` Eric Blake
2015-03-04  7:14   ` [Qemu-trivial] " Markus Armbruster
2015-03-04  7:14     ` Markus Armbruster
2015-03-04  8:53     ` zhanghailiang [this message]
2015-03-04  8:53       ` zhanghailiang
2015-03-04  8:45   ` [Qemu-trivial] " zhanghailiang
2015-03-04  8:45     ` 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=54F6C826.1010209@huawei.com \
    --to=zhang.zhanghailiang@huawei.com \
    --cc=armbru@redhat.com \
    --cc=eblake@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 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.