From: kbuild test robot <lkp@intel.com>
To: Shawn Lin <shawn.lin@rock-chips.com>
Cc: kbuild-all@01.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Shawn Lin <shawn.lin@rock-chips.com>
Subject: Re: [PATCH] PCI/MSI: Simplify the return value of arch_setup_msi_irqs
Date: Wed, 22 Jun 2016 11:08:50 +0800 [thread overview]
Message-ID: <201606221127.4pfm7CsI%fengguang.wu@intel.com> (raw)
In-Reply-To: <1466561915-25929-1-git-send-email-shawn.lin@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 2699 bytes --]
Hi,
[auto build test WARNING on pci/next]
[also build test WARNING on v4.7-rc4 next-20160621]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Shawn-Lin/PCI-MSI-Simplify-the-return-value-of-arch_setup_msi_irqs/20160622-103824
base: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
config: i386-defconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
In file included from include/linux/preempt.h:10:0,
from include/linux/spinlock.h:50,
from include/linux/mmzone.h:7,
from include/linux/gfp.h:5,
from include/linux/mm.h:9,
from drivers/pci/msi.c:10:
drivers/pci/msi.c: In function 'arch_setup_msi_irqs':
include/linux/list.h:447:2: warning: this 'for' clause does not guard... [-Wmisleading-indentation]
for (pos = list_first_entry(head, typeof(*pos), member); \
^
>> include/linux/msi.h:108:2: note: in expansion of macro 'list_for_each_entry'
list_for_each_entry((desc), dev_to_msi_list((dev)), list)
^~~~~~~~~~~~~~~~~~~
>> include/linux/msi.h:113:2: note: in expansion of macro 'for_each_msi_entry'
for_each_msi_entry((desc), &(pdev)->dev)
^~~~~~~~~~~~~~~~~~
>> drivers/pci/msi.c:122:2: note: in expansion of macro 'for_each_pci_msi_entry'
for_each_pci_msi_entry(entry, dev)
^~~~~~~~~~~~~~~~~~~~~~
drivers/pci/msi.c:124:3: note: ...this statement, but the latter is misleadingly indented as if it is guarded by the 'for'
if (ret)
^~
vim +/for_each_pci_msi_entry +122 drivers/pci/msi.c
106
107 int __weak arch_setup_msi_irqs(struct pci_dev *dev, int nvec, int type)
108 {
109 struct msi_controller *chip = dev->bus->msi;
110 struct msi_desc *entry;
111 int ret = 0;
112
113 if (chip && chip->setup_irqs)
114 return chip->setup_irqs(chip, dev, nvec, type);
115 /*
116 * If an architecture wants to support multiple MSI, it needs to
117 * override arch_setup_msi_irqs()
118 */
119 if (type == PCI_CAP_ID_MSI && nvec > 1)
120 return 1;
121
> 122 for_each_pci_msi_entry(entry, dev)
123 ret = arch_setup_msi_irq(dev, entry);
124 if (ret)
125 return -ENOSPC;
126
127 return 0;
128 }
129
130 /*
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 24880 bytes --]
prev parent reply other threads:[~2016-06-22 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 2:18 [PATCH] PCI/MSI: Simplify the return value of arch_setup_msi_irqs Shawn Lin
2016-06-22 3:08 ` kbuild test robot [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=201606221127.4pfm7CsI%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=bhelgaas@google.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=shawn.lin@rock-chips.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).