qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] arm: soc-dma: use hwaddr instead of target_ulong in printf
Date: Fri, 4 Dec 2015 13:36:40 +0100	[thread overview]
Message-ID: <566188D8.6010002@redhat.com> (raw)
In-Reply-To: <CAFEAcA948MpTBtiygPH0PQa2rrHS7xQycyr9PApXkFU=GaW1Rw@mail.gmail.com>



On 04/12/2015 13:33, Peter Maydell wrote:
> On 4 December 2015 at 12:28, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> This is a first baby step towards removing widespread inclusion of
>> cpu.h and compiling more devices once (so that arm, aarch64 and
>> in the future target-multi can share the object files).
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>>  hw/dma/soc_dma.c | 37 ++++++++++++++++---------------------
>>  1 file changed, 16 insertions(+), 21 deletions(-)
>>
>> diff --git a/hw/dma/soc_dma.c b/hw/dma/soc_dma.c
>> index c06aabb..ac395c5 100644
>> --- a/hw/dma/soc_dma.c
>> +++ b/hw/dma/soc_dma.c
>> @@ -269,11 +269,10 @@ void soc_dma_port_add_fifo(struct soc_dma_s *soc, hwaddr virt_base,
>>          if (entry->type == soc_dma_port_mem) {
>>              if (entry->addr <= virt_base &&
>>                              entry->addr + entry->u.mem.size > virt_base) {
>> -                fprintf(stderr, "%s: FIFO at " TARGET_FMT_lx
>> -                                " collides with RAM region at " TARGET_FMT_lx
>> -                                "-" TARGET_FMT_lx "\n", __FUNCTION__,
>> -                                (target_ulong) virt_base,
>> -                                (target_ulong) entry->addr, (target_ulong)
>> +                fprintf(stderr, "%s: FIFO at %"PRIx64
>> +                                " collides with RAM region at %"PRIx64
>> +                                "-%"PRIx64 "\n", __FUNCTION__,
>> +                                virt_base, entry->addr,
>>                                  (entry->addr + entry->u.mem.size));
> 
> Is using the HWADDR_PRI* macros for printing hwaddrs deprecated now?

It's the first time I hear about them. :)  There are still 130-odd
usages of HWADDR_PRIx and friends, so at least it's an incomplete
transition.  So I can use them if the maintainer tells me to.

Paolo

  reply	other threads:[~2015-12-04 12:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 12:28 [Qemu-devel] [PATCH] arm: soc-dma: use hwaddr instead of target_ulong in printf Paolo Bonzini
2015-12-04 12:28 ` [Qemu-devel] [PATCH] arm: explicitly mark loads as little-endian Paolo Bonzini
2015-12-04 12:51   ` Peter Maydell
2015-12-15 11:24   ` Peter Maydell
2015-12-04 12:33 ` [Qemu-devel] [PATCH] arm: soc-dma: use hwaddr instead of target_ulong in printf Peter Maydell
2015-12-04 12:36   ` Paolo Bonzini [this message]
2015-12-04 13:09     ` Peter Maydell
2015-12-04 16:39       ` Paolo Bonzini
2015-12-04 16:52         ` Peter Maydell
2015-12-15 11:28           ` Peter Maydell
2015-12-15 11:32             ` Paolo Bonzini
2015-12-04 12:55 ` Markus Armbruster

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=566188D8.6010002@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).