From: Paolo Bonzini <pbonzini@redhat.com>
To: Ed Maste <emaste@freebsd.org>
Cc: qemu-trivial@nongnu.org, Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-trivial] [PATCH for-1.5 v2] Rename hexdump to avoid FreeBSD libutil conflict
Date: Fri, 17 May 2013 09:32:52 +0200 [thread overview]
Message-ID: <5195DD24.10404@redhat.com> (raw)
In-Reply-To: <1368718348-15199-1-git-send-email-emaste@freebsd.org>
Il 16/05/2013 17:32, Ed Maste ha scritto:
> On FreeBSD libutil is used for openpty(), but it also provides a hexdump()
> which conflicts with QEMU's.
>
> Signed-off-by: Ed Maste <emaste@freebsd.org>
> ---
> v1->v2: Add hexdump() use in iov.c
>
> If desired I can workaround this via #define hacks in qemu-common.h
> instead; please let me know and I will submit that patch. This is needed
> to build on FreeBSD.
No, it's fine and should be in 1.5 given the delay.
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
> hw/dma/pl330.c | 4 ++--
> include/qemu-common.h | 2 +-
> util/hexdump.c | 2 +-
> util/iov.c | 2 +-
> 4 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/hw/dma/pl330.c b/hw/dma/pl330.c
> index 8b33138..60f5299 100644
> --- a/hw/dma/pl330.c
> +++ b/hw/dma/pl330.c
> @@ -1157,7 +1157,7 @@ static int pl330_exec_cycle(PL330Chan *channel)
> if (PL330_ERR_DEBUG > 1) {
> DB_PRINT("PL330 read from memory @%08x (size = %08x):\n",
> q->addr, len);
> - hexdump((char *)buf, stderr, "", len);
> + qemu_hexdump((char *)buf, stderr, "", len);
> }
> fifo_res = pl330_fifo_push(&s->fifo, buf, len, q->tag);
> if (fifo_res == PL330_FIFO_OK) {
> @@ -1189,7 +1189,7 @@ static int pl330_exec_cycle(PL330Chan *channel)
> if (PL330_ERR_DEBUG > 1) {
> DB_PRINT("PL330 read from memory @%08x (size = %08x):\n",
> q->addr, len);
> - hexdump((char *)buf, stderr, "", len);
> + qemu_hexdump((char *)buf, stderr, "", len);
> }
> if (q->inc) {
> q->addr += len;
> diff --git a/include/qemu-common.h b/include/qemu-common.h
> index 7f18b8e..b9057d1 100644
> --- a/include/qemu-common.h
> +++ b/include/qemu-common.h
> @@ -443,7 +443,7 @@ int mod_utf8_codepoint(const char *s, size_t n, char **end);
> * Hexdump a buffer to a file. An optional string prefix is added to every line
> */
>
> -void hexdump(const char *buf, FILE *fp, const char *prefix, size_t size);
> +void qemu_hexdump(const char *buf, FILE *fp, const char *prefix, size_t size);
>
> /* vector definitions */
> #ifdef __ALTIVEC__
> diff --git a/util/hexdump.c b/util/hexdump.c
> index 0d0efc8..969b340 100644
> --- a/util/hexdump.c
> +++ b/util/hexdump.c
> @@ -15,7 +15,7 @@
>
> #include "qemu-common.h"
>
> -void hexdump(const char *buf, FILE *fp, const char *prefix, size_t size)
> +void qemu_hexdump(const char *buf, FILE *fp, const char *prefix, size_t size)
> {
> unsigned int b;
>
> diff --git a/util/iov.c b/util/iov.c
> index 78bbbe1..cc6e837 100644
> --- a/util/iov.c
> +++ b/util/iov.c
> @@ -225,7 +225,7 @@ void iov_hexdump(const struct iovec *iov, const unsigned int iov_cnt,
> size = size > limit ? limit : size;
> buf = g_malloc(size);
> iov_to_buf(iov, iov_cnt, 0, buf, size);
> - hexdump(buf, fp, prefix, size);
> + qemu_hexdump(buf, fp, prefix, size);
> g_free(buf);
> }
>
>
prev parent reply other threads:[~2013-05-17 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 15:32 [Qemu-trivial] [PATCH v2] Rename hexdump to avoid FreeBSD libutil conflict Ed Maste
2013-05-17 7:32 ` Paolo Bonzini [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=5195DD24.10404@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=emaste@freebsd.org \
--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).