From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
Jonathan Corbet <corbet@lwn.net>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
linux-pci@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] Documentation: PCI: Update header defining struct pci_device_id
Date: Mon, 6 Jul 2026 12:41:11 +0200 [thread overview]
Message-ID: <akuF--S3u2ighG47@monoceros> (raw)
In-Reply-To: <a01d1cca33187c8b2715227d3db7146465513ced.1783332821.git.u.kleine-koenig@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
On Mon, Jul 06, 2026 at 12:21:15PM +0200, Uwe Kleine-König (The Capable Hub) wrote:
> The defintion of struct pci_device_id was moved from
> <linux/mod_devicetable.h> to a PCI specific header. Follow the movement
> to get the struct's documenation back.
>
> Fixes: ad428f5811bd ("mod_devicetable.h: Split into per subsystem headers")
> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
> ---
> Hello,
>
> I'm unsure about the best way to apply it. The obvious options are:
>
> - Linus applies it as he also pulled the header split without involving the
> PCI tree; or
> - it goes in via the pci tree
> - it goes in via the documentation tree
>
> The 2nd is probably preferable if there are pending pci fixes for 7.2
> anyhow?!
There are a few more instances that need a similar fix. So please
disregard this patch, I'll post a complete patch adapting all the now
broken references and target for the first or third option then.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-07-06 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 10:21 [PATCH v1] Documentation: PCI: Update header defining struct pci_device_id Uwe Kleine-König (The Capable Hub)
2026-07-06 10:41 ` 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=akuF--S3u2ighG47@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=torvalds@linux-foundation.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