From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: chunkeey@gmail.com
Subject: Re: [1/2] powerpc/4xx/ocm: Fix phys_addr_t printf warnings
Date: Wed, 2 Jan 2019 22:31:50 +1100 (AEDT) [thread overview]
Message-ID: <43V85g033hz9sCX@ozlabs.org> (raw)
In-Reply-To: <20190101035601.13200-1-mpe@ellerman.id.au>
On Tue, 2019-01-01 at 03:56:00 UTC, Michael Ellerman wrote:
> Currently the code produces several warnings, eg:
>
> arch/powerpc/platforms/4xx/ocm.c:240:38: error: format '%llx'
> expects argument of type 'long long unsigned int', but argument 3
> has type 'phys_addr_t {aka unsigned int}'
> seq_printf(m, "PhysAddr : 0x%llx\n", ocm->phys);
> ~~~^ ~~~~~~~~~
>
> Fix it by using the special %pa[p] format for printing phys_addr_t.
> Note we need to pass the value by reference for the special specifier
> to work.
>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Series applied to powerpc fixes.
https://git.kernel.org/powerpc/c/52b88fa1e8c7bae03bb691178a9f8b
cheers
next prev parent reply other threads:[~2019-01-02 11:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 3:56 [PATCH 1/2] powerpc/4xx/ocm: Fix phys_addr_t printf warnings Michael Ellerman
2019-01-01 3:56 ` [PATCH 2/2] powerpc/configs: Add PPC4xx_OCM to ppc40x_defconfig Michael Ellerman
2019-01-01 16:52 ` [PATCH 1/2] powerpc/4xx/ocm: Fix phys_addr_t printf warnings LEROY Christophe
2019-01-02 11:12 ` Michael Ellerman
2019-01-02 11:31 ` Michael Ellerman [this message]
2019-01-04 20:46 ` [1/2] " Christian Lamparter
2019-01-08 9:54 ` Michael Ellerman
2019-01-08 17:21 ` Christian Lamparter
2019-01-11 13:10 ` Michael Ellerman
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=43V85g033hz9sCX@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=chunkeey@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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.