From: Jason Wang <jasowang@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
Isaac Lozano <109lozanoi@gmail.com>,
qemu-devel@nongnu.org
Cc: Peter Crosthwaite <crosthwaitepeter@gmail.com>,
jsnow@redhat.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] util: Improved qemu_hexmap() to include an ascii dump of the buffer
Date: Fri, 1 Apr 2016 09:51:35 +0800 [thread overview]
Message-ID: <56FDD427.7010509@redhat.com> (raw)
In-Reply-To: <56FB7DD0.7070501@redhat.com>
On 03/30/2016 03:18 PM, Thomas Huth wrote:
> There's a typo in the title: qemu_hexmap should be qemu_hexdump/ instead.
>
> On 25.03.2016 11:42, Isaac Lozano wrote:
>> qemu_hexdump() in util/hexdump.c has been changed to give also include a
>> ascii dump of the buffer. Also, calls to hex_dump() in net/net.c have
>> been replaced with calls to qemu_hexdump(). This takes care of two misc
>> BiteSized Tasks.
>>
>> Signed-off-by: Isaac Lozano <109lozanoi@gmail.com>
>> ---
>>
>> v2: Fixed code-style and made debug line smaller.
>>
>> net/net.c | 30 +-----------------------------
>> util/hexdump.c | 33 ++++++++++++++++++++++-----------
>> 2 files changed, 23 insertions(+), 40 deletions(-)
> [...]
>
> Code looks fine now, thanks for taking care of this!
>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
>
> Jason, since there is no explicit maintainer for util/hexdump.c, could
> you maybe take this through your net tree, since this patch touches
> net/net.c as well?
Yes, applied in -net.
Thanks
>
> Thomas
>
>
next prev parent reply other threads:[~2016-04-01 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 10:42 [Qemu-devel] [PATCH v2] util: Improved qemu_hexmap() to include an ascii dump of the buffer Isaac Lozano
2016-03-30 7:18 ` Thomas Huth
2016-04-01 1:51 ` Jason Wang [this message]
2016-03-30 9:27 ` Gerd Hoffmann
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=56FDD427.7010509@redhat.com \
--to=jasowang@redhat.com \
--cc=109lozanoi@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=jsnow@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).