From: Philipp Stanner <pstanner@redhat.com>
To: Jonathan Corbet <corbet@lwn.net>, Arnd Bergmann <arnd@arndb.de>,
Michael Ellerman <mpe@ellerman.id.au>,
Helge Deller <deller@gmx.de>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Baoquan He <bhe@redhat.com>, Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, Philipp Stanner <pstanner@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [PATCH] Docu: fix build warnings for PCI
Date: Mon, 12 Feb 2024 16:09:34 +0100 [thread overview]
Message-ID: <20240212150934.24559-1-pstanner@redhat.com> (raw)
drivers/pci/iomap.c was accidentally added to the Documentation
generation at two places.
Remove it from Documentation/driver-api/device-io.rst to resolve the
collision.
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Closes: https://lore.kernel.org/all/20240205160908.6df5e790@canb.auug.org.au/
Fixes: 025bbeb5c880 ("lib: move pci_iomap.c to drivers/pci/")
Signed-off-by: Philipp Stanner <pstanner@redhat.com>
---
As discussed with Bjorn; this will be squashed into the series that
caused the problem, in PCI.
---
Documentation/driver-api/device-io.rst | 3 ---
1 file changed, 3 deletions(-)
diff --git a/Documentation/driver-api/device-io.rst b/Documentation/driver-api/device-io.rst
index d9ba2dfd1239..5c7e8194bef9 100644
--- a/Documentation/driver-api/device-io.rst
+++ b/Documentation/driver-api/device-io.rst
@@ -517,6 +517,3 @@ Public Functions Provided
.. kernel-doc:: arch/x86/include/asm/io.h
:internal:
-
-.. kernel-doc:: drivers/pci/iomap.c
- :export:
--
2.43.0
next reply other threads:[~2024-02-12 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 15:09 Philipp Stanner [this message]
2024-02-12 17:08 ` [PATCH] Docu: fix build warnings for PCI Bjorn Helgaas
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=20240212150934.24559-1-pstanner@redhat.com \
--to=pstanner@redhat.com \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=deller@gmx.de \
--cc=glaubitz@physik.fu-berlin.de \
--cc=helgaas@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).