linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Burton <paul.burton@mips.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
	"joe@perches.com" <joe@perches.com>,
	"Florian Fainelli" <f.fainelli@gmail.com>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
	"open list" <linux-kernel@vger.kernel.org>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] firmware: bcm47xx_nvram: Correct size_t printf format
Date: Mon, 26 Aug 2019 11:04:39 +0000	[thread overview]
Message-ID: <MWHPR2201MB12778655852AC1111F8B0E2CC1A10@MWHPR2201MB1277.namprd22.prod.outlook.com> (raw)
In-Reply-To: <20190514173816.17030-1-f.fainelli@gmail.com>

Hello,

Florian Fainelli wrote:
> When building on a 64-bit host, we will get warnings like those:
> 
> drivers/firmware/broadcom/bcm47xx_nvram.c:103:3: note: in expansion of macro 'pr_err'
>    pr_err("nvram on flash (%i bytes) is bigger than the reserved space in memory, will just copy the first %i bytes\n",
>    ^~~~~~
> drivers/firmware/broadcom/bcm47xx_nvram.c:103:28: note: format string is defined here
>    pr_err("nvram on flash (%i bytes) is bigger than the reserved space in memory, will just copy the first %i bytes\n",
>                            ~^
>                            %li
> 
> Use %zu instead for that purpose.

Series applied to mips-next.

> firmware: bcm47xx_nvram: Correct size_t printf format
>   commit feb4eb060c3a
>   https://git.kernel.org/mips/c/feb4eb060c3a
>   
>   Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>   Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>   Signed-off-by: Paul Burton <paul.burton@mips.com>
> 
> firmware: bcm47xx_nvram: Allow COMPILE_TEST
>   commit 5699ad0aaf10
>   https://git.kernel.org/mips/c/5699ad0aaf10
>   
>   Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>   Signed-off-by: Paul Burton <paul.burton@mips.com>

Thanks,
    Paul

[ This message was auto-generated; if you believe anything is incorrect
  then please email paul.burton@mips.com to report it. ]

      parent reply	other threads:[~2019-08-26 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 17:38 [PATCH v2 1/2] firmware: bcm47xx_nvram: Correct size_t printf format Florian Fainelli
2019-05-14 17:38 ` [PATCH v2 2/2] firmware: bcm47xx_nvram: Allow COMPILE_TEST Florian Fainelli
2019-05-15  5:17 ` [PATCH v2 1/2] firmware: bcm47xx_nvram: Correct size_t printf format Philippe Mathieu-Daudé
2019-08-26 11:04 ` Paul Burton [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=MWHPR2201MB12778655852AC1111F8B0E2CC1A10@MWHPR2201MB1277.namprd22.prod.outlook.com \
    --to=paul.burton@mips.com \
    --cc=f.fainelli@gmail.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=zajec5@gmail.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;
as well as URLs for NNTP newsgroup(s).