All of lore.kernel.org
 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 11:39:17 -0500 (EST)	[thread overview]
Message-ID: <22021448.34105148.1449247157194.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAFEAcA8k6dfOhSGnntqyn46aa1hYeK_+tgGcZ4rP-poW-e8NUw@mail.gmail.com>


> I don't think we've ever said "we should transition away from HWADDR_*",
> but whether we should is an interesting question, which is why I asked.
> Does retaining the format macros to go with the typedef give us
> useful flexibility, or is it just confusing?

I think it's confusing, but not enough to warrant a tree-wide search
and replace.

Paolo

> (Also TARGET_FMT_plx, which is even more heavily used and now
> rather out of step with the type name.)
> 
> thanks
> -- PMM
> 

  reply	other threads:[~2015-12-04 16:39 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
2015-12-04 13:09     ` Peter Maydell
2015-12-04 16:39       ` Paolo Bonzini [this message]
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=22021448.34105148.1449247157194.JavaMail.zimbra@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 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.