mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
	 Jason Wang <jasowangio@gmail.com>
Cc: "Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
	"Eugenio Pérez" <eperezma@redhat.com>,
	virtualization@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] virtio-pci: Drop inclusion of <linux/mod_devicetable.h>
Date: Wed, 11 Nov 2026 10:14:05 +0100	[thread overview]
Message-ID: <avQxWzMfc2LSe5tS@monoceros> (raw)
In-Reply-To: <fc69191474ffd49d50d7e39b13dfe6586f4d3f75.1783354857.git.u.kleine-koenig@baylibre.com>

[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]

Hello,

On Mon, Jul 06, 2026 at 06:22:08PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> Among the different device id structures <linux/virtio_pci_legacy.h>
> only uses struct virtio_device_id. Include <linux/device-id/virtio.h>
> instead of <linux/mod_devicetable.h> to provide that which is more
> lightweight and doesn't introduce that many dependencies.
> 
> The users of <linux/virtio_pci_legacy.h> also don't rely on this header
> to provide the full plethora of definitions. (There are only
> drivers/vdpa/alibaba/eni_vdpa.c and drivers/virtio/virtio_pci_common.c
> using pci_device_id and these include <linux/pci.h> which is enough to
> get it.)
> 
> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
> ---
> Hello,
> 
> note that <linux/device-id/virtio.h> only exists since v7.2-rc2, so make
> sure your base is new enough when applying this patch.

In case you postponed applying this patch because of that, I think it's
safe to assume that <linux/device-id/virtio.h> now exists in the
relevant tree.

The patch still applies fine to next-20261110, can you please apply it?

Best regards
Uwe

>  include/linux/virtio_pci_legacy.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/virtio_pci_legacy.h b/include/linux/virtio_pci_legacy.h
> index a8dc757d0367..96a9523e985d 100644
> --- a/include/linux/virtio_pci_legacy.h
> +++ b/include/linux/virtio_pci_legacy.h
> @@ -2,7 +2,7 @@
>  #ifndef _LINUX_VIRTIO_PCI_LEGACY_H
>  #define _LINUX_VIRTIO_PCI_LEGACY_H
>  
> -#include "linux/mod_devicetable.h"
> +#include <linux/device-id/virtio.h>
>  #include <linux/pci.h>
>  #include <linux/virtio_pci.h>
>  
> 
> base-commit: 8cdeaa50eae8dad34885515f62559ee83e7e8dda
> -- 
> 2.55.0.11.g153666a7d9bb
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2026-11-11  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 16:22 Uwe Kleine-König (The Capable Hub)
2026-11-11  9:14 ` Uwe Kleine-König (The Capable Hub) [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=avQxWzMfc2LSe5tS@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=eperezma@redhat.com \
    --cc=jasowangio@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=xuanzhuo@linux.alibaba.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

all inboxes | Powered by JetHome®