From: Bjorn Helgaas <helgaas@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [pci:review/vga] BUILD SUCCESS WITH WARNING b6f0a577c4fbcc4f1e7eaf0e9a30bcfd20002b44
Date: Thu, 22 Jul 2021 14:51:04 -0500 [thread overview]
Message-ID: <20210722195104.GA336804@bjorn-Precision-5520> (raw)
In-Reply-To: <20210722193529.GA333109@bjorn-Precision-5520>
On Thu, Jul 22, 2021 at 02:35:29PM -0500, Bjorn Helgaas wrote:
> On Thu, Jul 22, 2021 at 02:06:19PM +0800, kernel test robot wrote:
> > tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git review/vga
> > branch HEAD: b6f0a577c4fbcc4f1e7eaf0e9a30bcfd20002b44 FIXME PCI/VGA: Rework default VGA device selection
> >
> > possible Warning in current branch:
> >
> > drivers/pci/vgaarb.c:1045:8: warning: %d in format string (no. 6) requires 'int' but the argument type is 'unsigned int'. [invalidPrintfArgType_sint]
>
> At b6f0a577c4fb ("FIXME PCI/VGA: Rework default VGA device
> selection"), line 1045 in vgaarb.c does not contain a format string:
>
> 1042 #define PCI_INVALID_CARD ((struct pci_dev *)-1UL)
> 1043
> 1044 /*
> 1045 * Each user has an array of these, tracking which cards have locks
> 1046 */
> 1047 struct vga_arb_user_card {
> 1048 struct pci_dev *pdev;
>
> Where's the info so I can reproduce this? Compiler version and
> options, .config file, etc?
Never mind, I think I found it manually. At 4e5cfb7f1564 ("PCI/VGA:
Move vgaarb to drivers/pci"), line 1045 *was* an snprintf that used %d
for unsigned values.
> > Warning ids grouped by kconfigs:
> >
> > gcc_recent_errors
> > `-- arm-randconfig-p001-20210720
> > `-- drivers-pci-vgaarb.c:warning:d-in-format-string-(no.-)-requires-int-but-the-argument-type-is-unsigned-int-.-invalidPrintfArgType_sint
prev parent reply other threads:[~2021-07-22 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 6:06 [pci:review/vga] BUILD SUCCESS WITH WARNING b6f0a577c4fbcc4f1e7eaf0e9a30bcfd20002b44 kernel test robot
2021-07-22 19:35 ` Bjorn Helgaas
2021-07-22 19:51 ` Bjorn Helgaas [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=20210722195104.GA336804@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.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