From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v2] vfio/pci: Mask buggy SR-IOV VF INTx support
Date: Thu, 20 Sep 2018 22:53:04 -0700
Message-ID: <20180921055304.GA12584@infradead.org>
References: <153747346143.7344.14634545723456004489.stgit@gimli.home>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm@vger.kernel.org, ashok.raj@intel.com, gage.eads@intel.com,
        gnomes@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
To: Alex Williamson <alex.williamson@redhat.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <153747346143.7344.14634545723456004489.stgit@gimli.home>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org

> +/*
> + * 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?