From: Hannes Reinecke <hare@suse.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: Build warning regression (104daa71b396 ("PCI: Determine actual VPD size on first access"))
Date: Tue, 10 May 2016 08:09:53 +0200 [thread overview]
Message-ID: <57317B31.8030203@suse.de> (raw)
In-Reply-To: <20160509195410.GB18166@localhost>
On 05/09/2016 09:54 PM, Bjorn Helgaas wrote:
> Hi Hannes,
>
> Geert's list of build regressions and improvements
> (http://lkml.kernel.org/r/1462782250-6231-1-git-send-email-geert@linux-m68k.org)
> shows these new warnings:
>
> drivers/pci/access.c: warning: format '%zu' expects argument of type 'size_t', but argument 4 has type 'unsigned int' [-Wformat=]: => 318:8
> drivers/pci/access.c: warning: format '%zu' expects argument of type 'size_t', but argument 5 has type 'unsigned int' [-Wformat=]: => 340:6
>
> which I think are due to 104daa71b396 ("PCI: Determine actual VPD size on
> first access").
>
> Would you mind fixing those up and sending me a patch? These were in
> the v4.6-rc1 regressions email, and I should have noticed then, but I
> didn't.
>
This is curious.
The code has this:
size_t off = 0;
...
dev_warn(&dev->dev,
"invalid large VPD tag %02x size at offset %zu",
tag, off + 1);
Which, as per my reading, suggests that the last argument to
dev_warn() is of type size_t.
Which tree has generated the above warning?
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-05-10 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 19:54 Build warning regression (104daa71b396 ("PCI: Determine actual VPD size on first access")) Bjorn Helgaas
2016-05-10 6:09 ` Hannes Reinecke [this message]
2016-05-10 11:51 ` Bjorn Helgaas
2016-05-10 11:56 ` Geert Uytterhoeven
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=57317B31.8030203@suse.de \
--to=hare@suse.de \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.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).