From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [v2] powerpc/prom: fix early DEBUG messages
Date: Sat, 22 Dec 2018 20:54:45 +1100 (AEDT) [thread overview]
Message-ID: <43MLSj3Dh1z9sP9@ozlabs.org> (raw)
In-Reply-To: <a138aa8f635f3d9e49e8aa5e3fcfe271bf669b4d.1544749037.git.christophe.leroy@c-s.fr>
On Fri, 2018-12-14 at 10:27:47 UTC, Christophe Leroy wrote:
> This patch fixes early DEBUG messages in prom.c:
> - Use %px instead of %p to see the addresses
> - Cast memblock_phys_mem_size() with (unsigned long long) to
> avoid build failure when phys_addr_t is not 64 bits.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/b18f0ae92b0a1db565c3e505fa87b6
cheers
prev parent reply other threads:[~2018-12-22 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 10:27 [PATCH v2] powerpc/prom: fix early DEBUG messages Christophe Leroy
2018-12-22 9:54 ` Michael Ellerman [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=43MLSj3Dh1z9sP9@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).