From: Alex Williamson <alex.williamson@redhat.com>
To: James Puthukattukaran <james.puthukattukaran@oracle.com>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, Sinan Kaya <okaya@codeaurora.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH 1/2] PCI: Add pci_bus_specific_read_dev_vendor_id() to workaround PCI switch specific issues prior to accessing newly added endpoint
Date: Thu, 26 Apr 2018 13:42:30 -0600 [thread overview]
Message-ID: <20180426134230.3d0d55ca@w520.home> (raw)
In-Reply-To: <32d9b7ce-0993-c749-3285-a51146fe37d6@oracle.com>
On Thu, 26 Apr 2018 15:32:00 -0400
James Puthukattukaran <james.puthukattukaran@oracle.com> wrote:
> On 04/26/2018 02:26 AM, kbuild test robot wrote:
> > Hi James,
> >
> > Thank you for the patch! Yet something to improve:
> >
> > [auto build test ERROR on pci/next]
> > [also build test ERROR on v4.17-rc2 next-20180424]
> > [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/James-Puthukattukaran/PCI-SUpport-to-workaround-bus-level-HW-issues/20180426-092305
> > base: https://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
> > config: ia64-allnoconfig (attached as .config)
> > compiler: ia64-linux-gcc (GCC) 7.2.0
> > reproduce:
> > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > chmod +x ~/bin/make.cross
> > # save the attached .config to linux build tree
> > make.cross ARCH=ia64
> >
> > All errors (new ones prefixed by >>):
> >
> > drivers/pci/probe.o: In function `pci_bus_read_dev_vendor_id':
> >>> probe.c:(.text+0x3e02): undefined reference to `pci_bus_specific_read_dev_vendor_id'
>
> Alex/Sinan -
>
> Would it be an acceptable fix for this problem?
>
>
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -2097,6 +2097,13 @@ static bool pci_bus_wait_crs(struct pci_bus *bus, int devfn, u32 *l,
> return true;
> }
>
> +int __weak pci_bus_specific_read_dev_vendor_id(struct pci_bus *bus, int devfn,
> + u32 *l, int timeout)
> +{
> + return -ENOTTY;
> +}
> +
> +
Close, but I'd suggest following the example set by other quirks,
generally there's a stub definition of it in pci.h when !#defined
CONFIG_PCI_QUIRKS. See for example pci_dev_specific_acs_enabled().
Thanks,
Alex
> bool pci_bus_generic_read_dev_vendor_id(struct pci_bus *bus, int devfn, u32 *l,
> int timeout)
> {
>
>
> I ran the repro steps and it completes without issues. In addition, I will fix the typos Alex pointed out in the last submission and resubmit.
> thanks
> James
next prev parent reply other threads:[~2018-04-26 19:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 14:51 [PATCH 0/2] PCI: SUpport to workaround bus level HW issues James Puthukattukaran
2018-04-24 14:53 ` [PATCH 1/2] PCI: Add pci_bus_specific_read_dev_vendor_id() to workaround PCI switch specific issues prior to accessing newly added endpoint James Puthukattukaran
2018-04-24 17:50 ` Alex Williamson
2018-04-26 6:26 ` kbuild test robot
2018-04-26 19:32 ` James Puthukattukaran
2018-04-26 19:42 ` Alex Williamson [this message]
2018-04-26 19:45 ` Sinan Kaya
2018-04-26 8:53 ` kbuild test robot
2018-04-24 14:54 ` [PATCH 2/2] PCI: Implement workaround for the ACS bug in the IDT switch James Puthukattukaran
2018-04-24 17:50 ` Alex Williamson
-- strict thread matches above, loose matches on Subject: below --
2018-04-19 17:36 [PATCH 0/2] PCI: Support to workaround bus level HW issues James Puthukattukaran
2018-04-19 17:37 ` [PATCH 1/2] PCI: Add pci_bus_specific_read_dev_vendor_id() to workaround PCI switch specific issues prior to accessing newly added endpoint James Puthukattukaran
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=20180426134230.3d0d55ca@w520.home \
--to=alex.williamson@redhat.com \
--cc=james.puthukattukaran@oracle.com \
--cc=kbuild-all@01.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=okaya@codeaurora.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).