[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjmJbF3p9vZTW2nbeD4LkG-JZV+uqv8BnxzojJ5SZsLjw@mail.gmail.com>
Date: Sun, 22 Sep 2019 11:35:36 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Paul Burton <paul.burton@...s.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>
Subject: Re: [GIT PULL] MIPS changes
On Sat, Sep 21, 2019 at 4:10 PM Paul Burton <paul.burton@...s.com> wrote:
>
> Here are the main MIPS changes for v5.4; please pull.
Hmm. I pulled and because initial tests didn't show any issues, I
already pushed out.
But some unrelated further testing then shows that this:
> Florian Fainelli (2):
> firmware: bcm47xx_nvram: Correct size_t printf format
> firmware: bcm47xx_nvram: Allow COMPILE_TEST
causes problems, and commit feb4eb060c3a ("firmware: bcm47xx_nvram:
Correct size_t printf format") is buggy:
drivers/firmware/broadcom/bcm47xx_nvram.c: In function ‘nvram_init’:
drivers/firmware/broadcom/bcm47xx_nvram.c:151: warning: format ‘%zu’
expects argument of type ‘size_t’, but argument 2 has type ‘u32’ {aka
‘unsigned int’} [-Wformat=]
and the change to use %zu was completely wrong.
It prints out 'header.len', which is an u32, not nvram_len which is a size_t.
Tssk tssk.
I've fixed it in my tree, but this should have shown up in linux-next,
or in MIPS testing. The process clearly failed.
Linus
Powered by blists - more mailing lists