From: Christoph Hellwig <hch@infradead.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, ashok.raj@intel.com, gage.eads@intel.com,
gnomes@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] vfio/pci: Mask buggy SR-IOV VF INTx support
Date: Thu, 20 Sep 2018 22:53:04 -0700 [thread overview]
Message-ID: <20180921055304.GA12584@infradead.org> (raw)
In-Reply-To: <153747346143.7344.14634545723456004489.stgit@gimli.home>
> +/*
> + * Nag about hardware bugs, hopefully to have vendors fix them, but at least
> + * to collect a list of dependencies for the VF INTx pin quirk below.
> + */
> +static const struct pci_device_id known_bogus_vf_intx_pin[] = {
> + { PCI_DEVICE(PCI_VENDOR_ID_INTEL, 0x270c) },
> + {}
> +};
What device is this? We don't have the device ID anywhere, so I guess
it is something match by the class code?
next prev parent reply other threads:[~2018-09-21 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 20:03 [PATCH v2] vfio/pci: Mask buggy SR-IOV VF INTx support Alex Williamson
2018-09-20 22:56 ` Eads, Gage
2018-09-20 22:58 ` Raj, Ashok
2018-09-21 5:53 ` Christoph Hellwig [this message]
2018-09-21 15:16 ` Alex Williamson
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=20180921055304.GA12584@infradead.org \
--to=hch@infradead.org \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=gage.eads@intel.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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).