[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+7wUsy8=hbyN4NQ3x-Sp-YT1uPFRcYLNpJncuoMMy==Qd7PeQ@mail.gmail.com>
Date: Tue, 29 May 2018 14:14:27 +0200
From: Mathieu Malaterre <malat@...ian.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Michael Ellerman <mpe@...erman.id.au>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
PowerPC <linuxppc-dev@...ts.ozlabs.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: boot messages from today's linux-next
Michael,
On Tue, May 29, 2018 at 2:00 PM, Mathieu Malaterre <malat@...ian.org> wrote:
> On Tue, May 29, 2018 at 1:56 PM, Mathieu Malaterre <malat@...ian.org> wrote:
>> On Tue, May 29, 2018 at 1:02 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>>> Hi all,
>>>
>>> My qemu boots of today's powerpc linux-next kernel produced the following
>>> boot message differences:
>>>
>>> -Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
>>> +Max number of cores passed to firmware: u (NR_CPUS = 2048)
>>>
>>> Seemingly caused by commit
>>>
>>> eae5f709a4d7 ("powerpc: Add __printf verification to prom_printf")
>>
>> My bad. Patch is pending (thanks Michael!):
>>
>> https://patchwork.ozlabs.org/patch/921948/
>
> Nope, nevermind this is unrelated.
Could you update your patch "powerpc/prom: Fix %llx usage since
prom_printf() change" to also do "powerpc/prom: Fix %u usage since
prom_printf() change"
I did not pay attention that "%u" was also not supported in prom_printf.
I may be able to provide a patch tonight, if this is not acceptable,
please revert my faulty patch. Sorry for the mess.
>>> --
>>> Cheers,
>>> Stephen Rothwell
Powered by blists - more mailing lists