From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org, agraf@suse.de, scottwood@freescale.com,
jasowang@redhat.com, Andrey Smirnov <andrew.smirnov@gmail.com>
Subject: [Qemu-devel] [PATCH 2/2] fsl_etsec: Fix various small problems in hexdump code
Date: Mon, 28 Nov 2016 10:13:15 -0800 [thread overview]
Message-ID: <1480356795-8043-2-git-send-email-andrew.smirnov@gmail.com> (raw)
In-Reply-To: <1480356795-8043-1-git-send-email-andrew.smirnov@gmail.com>
Fix various small problems in hexdump code, such as:
- Reference to non-existing field etsec->nic->nc.name is replaced
with nc->name
- Type mismatch warnings
Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com>
---
hw/net/fsl_etsec/etsec.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/net/fsl_etsec/etsec.c b/hw/net/fsl_etsec/etsec.c
index b5c777f..1093d8b 100644
--- a/hw/net/fsl_etsec/etsec.c
+++ b/hw/net/fsl_etsec/etsec.c
@@ -348,8 +348,8 @@ static ssize_t etsec_receive(NetClientState *nc,
eTSEC *etsec = qemu_get_nic_opaque(nc);
#if defined(HEX_DUMP)
- fprintf(stderr, "%s receive size:%d\n", etsec->nic->nc.name, size);
- qemu_hexdump(buf, stderr, "", size);
+ fprintf(stderr, "%s receive size:%zd\n", nc->name, size);
+ qemu_hexdump((void *)buf, stderr, "", size);
#endif
/* Flush is unnecessary as are already in receiving path */
etsec->need_flush = false;
--
2.5.5
next prev parent reply other threads:[~2016-11-28 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 18:13 [Qemu-devel] [PATCH 1/2] fsl_etsec: Pad short payloads with zeros Andrey Smirnov
2016-11-28 18:13 ` Andrey Smirnov [this message]
2016-11-30 10:41 ` [Qemu-devel] [PATCH 2/2] fsl_etsec: Fix various small problems in hexdump code Jason Wang
2016-11-30 10:41 ` [Qemu-devel] [PATCH 1/2] fsl_etsec: Pad short payloads with zeros Jason Wang
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=1480356795-8043-2-git-send-email-andrew.smirnov@gmail.com \
--to=andrew.smirnov@gmail.com \
--cc=agraf@suse.de \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=scottwood@freescale.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).