[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YMd1ZSCZLjaE4TFb@infradead.org>
Date: Mon, 14 Jun 2021 16:27:33 +0100
From: Christoph Hellwig <hch@...radead.org>
To: Max Gurtovoy <mgurtovoy@...dia.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Alex Williamson <alex.williamson@...hat.com>,
Jason Gunthorpe <jgg@...dia.com>, cohuck@...hat.com,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
aviadye@...dia.com, oren@...dia.com, shahafs@...dia.com,
parav@...dia.com, artemp@...dia.com, kwankhede@...dia.com,
ACurrid@...dia.com, cjia@...dia.com, yishaih@...dia.com,
kevin.tian@...el.com, targupta@...dia.com,
shameerali.kolothum.thodi@...wei.com, liulongfang@...wei.com,
yan.y.zhao@...el.com
Subject: Re: [PATCH 09/11] PCI: add matching checks for driver_override
binding
On Mon, Jun 14, 2021 at 11:18:32AM +0300, Max Gurtovoy wrote:
> * into a static list of equivalent device types,
> * instead of using it as a pointer.
> + * @flags: PCI flags of the driver. Bitmap of pci_id_flags enum.
> */
> struct pci_device_id {
> __u32 vendor, device; /* Vendor and device ID or PCI_ANY_ID*/
> __u32 subvendor, subdevice; /* Subsystem ID's or PCI_ANY_ID */
> __u32 class, class_mask; /* (class,subclass,prog-if) triplet */
> kernel_ulong_t driver_data; /* Data private to the driver */
> + __u32 flags;
> };
Isn't struct pci_device_id a userspace ABI due to MODULE_DEVICE_TABLE()?
Powered by blists - more mailing lists