All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Stuart Hayes <stuart.w.hayes@gmail.com>
Cc: kbuild-all@lists.01.org, Bjorn Helgaas <bhelgaas@google.com>,
	Austin Bolen <austin_bolen@dell.com>,
	keith.busch@intel.com, Alexandru Gagniuc <mr.nuke.me@gmail.com>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	"Gustavo A . R . Silva" <gustavo@embeddedor.com>,
	Sinan Kaya <okaya@kernel.org>,
	Oza Pawandeep <poza@codeaurora.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	lukas@wunner.de, Stuart Hayes <stuart.w.hayes@gmail.com>
Subject: Re: [PATCH] PCI: pciehp: Make sure pciehp_isr clears interrupt events
Date: Wed, 13 Nov 2019 20:13:04 +0800	[thread overview]
Message-ID: <201911132048.rcf6xpZS%lkp@intel.com> (raw)
In-Reply-To: <20191112215938.1145-1-stuart.w.hayes@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3827 bytes --]

Hi Stuart,

I love your patch! Perhaps something to improve:

[auto build test WARNING on pci/next]
[cannot apply to v5.4-rc7 next-20191111]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Stuart-Hayes/PCI-pciehp-Make-sure-pciehp_isr-clears-interrupt-events/20191113-174426
base:   https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

   drivers/pci/hotplug/pciehp_hpc.c: In function 'pciehp_isr':
>> drivers/pci/hotplug/pciehp_hpc.c:15:22: warning: format '%s' expects argument of type 'char *', but argument 3 has type 'int' [-Wformat=]
    #define dev_fmt(fmt) "pciehp: " fmt
                         ^
   include/linux/device.h:1743:17: note: in expansion of macro 'dev_fmt'
     _dev_warn(dev, dev_fmt(fmt), ##__VA_ARGS__)
                    ^~~~~~~
>> include/linux/pci.h:2377:37: note: in expansion of macro 'dev_warn'
    #define pci_warn(pdev, fmt, arg...) dev_warn(&(pdev)->dev, fmt, ##arg)
                                        ^~~~~~~~
>> drivers/pci/hotplug/pciehp.h:42:2: note: in expansion of macro 'pci_warn'
     pci_warn(ctrl->pcie->port, format, ## arg)
     ^~~~~~~~
>> drivers/pci/hotplug/pciehp_hpc.c:568:3: note: in expansion of macro 'ctrl_warn'
      ctrl_warn(ctrl, "Slot(%s): Hot plug event bit stuck, reading %x\n",
      ^~~~~~~~~
   drivers/pci/hotplug/pciehp_hpc.c:568:26: note: format string is defined here
      ctrl_warn(ctrl, "Slot(%s): Hot plug event bit stuck, reading %x\n",
                            ~^
                            %d
>> drivers/pci/hotplug/pciehp_hpc.c:15:22: warning: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'const char *' [-Wformat=]
    #define dev_fmt(fmt) "pciehp: " fmt
                         ^
   include/linux/device.h:1743:17: note: in expansion of macro 'dev_fmt'
     _dev_warn(dev, dev_fmt(fmt), ##__VA_ARGS__)
                    ^~~~~~~
>> include/linux/pci.h:2377:37: note: in expansion of macro 'dev_warn'
    #define pci_warn(pdev, fmt, arg...) dev_warn(&(pdev)->dev, fmt, ##arg)
                                        ^~~~~~~~
>> drivers/pci/hotplug/pciehp.h:42:2: note: in expansion of macro 'pci_warn'
     pci_warn(ctrl->pcie->port, format, ## arg)
     ^~~~~~~~
>> drivers/pci/hotplug/pciehp_hpc.c:568:3: note: in expansion of macro 'ctrl_warn'
      ctrl_warn(ctrl, "Slot(%s): Hot plug event bit stuck, reading %x\n",
      ^~~~~~~~~
   drivers/pci/hotplug/pciehp_hpc.c:568:65: note: format string is defined here
      ctrl_warn(ctrl, "Slot(%s): Hot plug event bit stuck, reading %x\n",
                                                                   ~^
                                                                   %s

vim +15 drivers/pci/hotplug/pciehp_hpc.c

94dbc9562edc74 Frederick Lawler 2019-05-07 @15  #define dev_fmt(fmt) "pciehp: " fmt
94dbc9562edc74 Frederick Lawler 2019-05-07  16  

:::::: The code at line 15 was first introduced by commit
:::::: 94dbc9562edc745d0549f1744ca1bd75e644473e PCI: pciehp: Log messages with pci_dev, not pcie_device

:::::: TO: Frederick Lawler <fred@fredlawl.com>
:::::: CC: Bjorn Helgaas <bhelgaas@google.com>

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 70182 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] PCI: pciehp: Make sure pciehp_isr clears interrupt events
Date: Wed, 13 Nov 2019 20:13:04 +0800	[thread overview]
Message-ID: <201911132048.rcf6xpZS%lkp@intel.com> (raw)
In-Reply-To: <20191112215938.1145-1-stuart.w.hayes@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3906 bytes --]

Hi Stuart,

I love your patch! Perhaps something to improve:

[auto build test WARNING on pci/next]
[cannot apply to v5.4-rc7 next-20191111]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Stuart-Hayes/PCI-pciehp-Make-sure-pciehp_isr-clears-interrupt-events/20191113-174426
base:   https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
config: x86_64-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-14) 7.4.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

   drivers/pci/hotplug/pciehp_hpc.c: In function 'pciehp_isr':
>> drivers/pci/hotplug/pciehp_hpc.c:15:22: warning: format '%s' expects argument of type 'char *', but argument 3 has type 'int' [-Wformat=]
    #define dev_fmt(fmt) "pciehp: " fmt
                         ^
   include/linux/device.h:1743:17: note: in expansion of macro 'dev_fmt'
     _dev_warn(dev, dev_fmt(fmt), ##__VA_ARGS__)
                    ^~~~~~~
>> include/linux/pci.h:2377:37: note: in expansion of macro 'dev_warn'
    #define pci_warn(pdev, fmt, arg...) dev_warn(&(pdev)->dev, fmt, ##arg)
                                        ^~~~~~~~
>> drivers/pci/hotplug/pciehp.h:42:2: note: in expansion of macro 'pci_warn'
     pci_warn(ctrl->pcie->port, format, ## arg)
     ^~~~~~~~
>> drivers/pci/hotplug/pciehp_hpc.c:568:3: note: in expansion of macro 'ctrl_warn'
      ctrl_warn(ctrl, "Slot(%s): Hot plug event bit stuck, reading %x\n",
      ^~~~~~~~~
   drivers/pci/hotplug/pciehp_hpc.c:568:26: note: format string is defined here
      ctrl_warn(ctrl, "Slot(%s): Hot plug event bit stuck, reading %x\n",
                            ~^
                            %d
>> drivers/pci/hotplug/pciehp_hpc.c:15:22: warning: format '%x' expects argument of type 'unsigned int', but argument 4 has type 'const char *' [-Wformat=]
    #define dev_fmt(fmt) "pciehp: " fmt
                         ^
   include/linux/device.h:1743:17: note: in expansion of macro 'dev_fmt'
     _dev_warn(dev, dev_fmt(fmt), ##__VA_ARGS__)
                    ^~~~~~~
>> include/linux/pci.h:2377:37: note: in expansion of macro 'dev_warn'
    #define pci_warn(pdev, fmt, arg...) dev_warn(&(pdev)->dev, fmt, ##arg)
                                        ^~~~~~~~
>> drivers/pci/hotplug/pciehp.h:42:2: note: in expansion of macro 'pci_warn'
     pci_warn(ctrl->pcie->port, format, ## arg)
     ^~~~~~~~
>> drivers/pci/hotplug/pciehp_hpc.c:568:3: note: in expansion of macro 'ctrl_warn'
      ctrl_warn(ctrl, "Slot(%s): Hot plug event bit stuck, reading %x\n",
      ^~~~~~~~~
   drivers/pci/hotplug/pciehp_hpc.c:568:65: note: format string is defined here
      ctrl_warn(ctrl, "Slot(%s): Hot plug event bit stuck, reading %x\n",
                                                                   ~^
                                                                   %s

vim +15 drivers/pci/hotplug/pciehp_hpc.c

94dbc9562edc74 Frederick Lawler 2019-05-07 @15  #define dev_fmt(fmt) "pciehp: " fmt
94dbc9562edc74 Frederick Lawler 2019-05-07  16  

:::::: The code at line 15 was first introduced by commit
:::::: 94dbc9562edc745d0549f1744ca1bd75e644473e PCI: pciehp: Log messages with pci_dev, not pcie_device

:::::: TO: Frederick Lawler <fred@fredlawl.com>
:::::: CC: Bjorn Helgaas <bhelgaas@google.com>

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 70182 bytes --]

  parent reply	other threads:[~2019-11-13 12:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 21:59 [PATCH] PCI: pciehp: Make sure pciehp_isr clears interrupt events Stuart Hayes
2019-11-13  4:59 ` Lukas Wunner
2019-11-13 21:58   ` Stuart Hayes
2019-11-14  2:50     ` Lukas Wunner
2019-11-13 12:13 ` kbuild test robot [this message]
2019-11-13 12:13   ` kbuild test robot
2019-11-25 21:03 ` Stuart Hayes
2019-11-26 23:37   ` Bjorn Helgaas
2019-11-27  0:06     ` Stuart Hayes

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=201911132048.rcf6xpZS%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=austin_bolen@dell.com \
    --cc=bhelgaas@google.com \
    --cc=gustavo@embeddedor.com \
    --cc=kbuild-all@lists.01.org \
    --cc=keith.busch@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=mika.westerberg@linux.intel.com \
    --cc=mr.nuke.me@gmail.com \
    --cc=okaya@kernel.org \
    --cc=poza@codeaurora.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=stuart.w.hayes@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.