From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Karl Mehltretter <kmehltretter@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Alexander Usyskin <alexander.usyskin@intel.com>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
Dongliang Mu <dzm91@hust.edu.cn>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Danilo Krummrich <dakr@kernel.org>,
Takashi Sakamoto <o-takashi@sakamocchi.jp>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-pci@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v3] Documentation: Update after split of <linux/mod_devicetable.h>
Date: Wed, 28 Oct 2026 09:03:55 +0100 [thread overview]
Message-ID: <auGsNgw50hDIdm3R@monoceros> (raw)
In-Reply-To: <87h5jq8gia.fsf@trenco.lwn.net>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
Hello Karl,
On Tue, Sep 15, 2026 at 01:24:29PM -0600, Jonathan Corbet wrote:
> Karl Mehltretter <kmehltretter@gmail.com> writes:
> > Most structs that were defined in <linux/mod_devicetable.h> before were
> > moved to a bus specific header. Follow the movement to get the struct's
> > documentation back.
> >
> > For the list of device ids in basics.rst use an explicit list of all the
> > headers that have kernel-doc annotations and that are not described
> > elsewhere (i.e. pci and mei_cl). <linux/device-id/acpi.h> is left out on
> > purpose, ACPI_DEVICE_CLASS() is not a device id struct.
> >
> > Also repair the referencing in the zh_CN translation of pci.rst and
> > don't duplicate `struct mei_cl_device_id`.
>
> This one adds some new build warnings:
>
> Documentation/translations/zh_CN/PCI/pci:98: ./include/linux/pci.h:3: WARNING: Duplicate C declaration, also defined at PCI/pci:3.
> Declaration is '.. c:struct:: pci_driver'. [duplicate_declaration.c]
> kernel/Documentation/translations/zh_CN/PCI/pci:106: ./include/linux/device-id/pci.h:3: WARNING: Duplicate C declaration, also defined at PCI/pci:3.
> Declaration is '.. c:struct:: pci_device_id'. [duplicate_declaration.c]
Do you intend to address this?
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-10-28 8:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 7:00 Karl Mehltretter
2026-09-08 8:29 ` Andy Shevchenko
2026-09-09 9:19 ` Uwe Kleine-König
2026-09-08 9:45 ` Uwe Kleine-König
2026-09-15 19:24 ` Jonathan Corbet
2026-10-28 8:03 ` Uwe Kleine-König [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=auGsNgw50hDIdm3R@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=alexander.usyskin@intel.com \
--cc=alexs@kernel.org \
--cc=andersson@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=dzm91@hust.edu.cn \
--cc=geert@linux-m68k.org \
--cc=kmehltretter@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=mathieu.poirier@linaro.org \
--cc=o-takashi@sakamocchi.jp \
--cc=rdunlap@infradead.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®