From: "Arnd Bergmann" <arnd@kernel.org>
To: "Christoph Hellwig" <hch@infradead.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>
Cc: "Desnes Nunes" <desnesn@redhat.com>,
"Christoph Hellwig" <hch@lst.de>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Robin Murphy" <robin.murphy@arm.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
"kernel test robot" <lkp@intel.com>,
noreply@ellerman.id.au
Subject: Re: [PATCH -next] dma-debug: Use %pa to format phys_addr_t
Date: Thu, 30 Mar 2023 08:51:15 +0200 [thread overview]
Message-ID: <5db9b27a-90df-4916-90da-4e8daeebf9e3@app.fastmail.com> (raw)
In-Reply-To: <ZCTOxOGDPoJoZDNW@infradead.org>
On Thu, Mar 30, 2023, at 01:50, Christoph Hellwig wrote:
> I've applied this as it is the first fix I got into my mailbox for it.
>
> Arnd sent one a little later, which uses %pap instead of %pa, which
> confused me a bit. The documentation seems to allow both without
> any recommendation which one to use, which confuses me even further.
Indeed, I wasn't aware of this either, apparently aaf07621b8bb
("vsprintf: add %pad extension for dma_addr_t use") introduced the
%pap form at the same time as %pad but made it the same as the already
existing %pa. I also see that the %pa form is a lot more common than
%pap, so it's probably better to go with %pa for new users anyway.
Arnd
next prev parent reply other threads:[~2023-03-30 6:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 7:14 Geert Uytterhoeven
2023-03-29 15:03 ` Jerry Snitselaar
2023-03-29 15:34 ` Geert Uytterhoeven
2023-03-29 15:38 ` Jerry Snitselaar
2023-03-29 23:50 ` Christoph Hellwig
2023-03-30 6:51 ` Arnd Bergmann [this message]
2023-03-30 7:07 ` Geert Uytterhoeven
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=5db9b27a-90df-4916-90da-4e8daeebf9e3@app.fastmail.com \
--to=arnd@kernel.org \
--cc=desnesn@redhat.com \
--cc=geert+renesas@glider.be \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=m.szyprowski@samsung.com \
--cc=noreply@ellerman.id.au \
--cc=robin.murphy@arm.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
all inboxes | Powered by JetHome®