From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>, Wolfram Sang <wsa@the-dreams.de>,
Peter Zijlstra <peterz@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-ide@vger.kernel.org, linux-i2c@vger.kernel.org,
Joel Fernandes <joel@joelfernandes.org>,
linux1394-devel@lists.sourceforge.net,
Will Deacon <will@kernel.org>, Jason Gunthorpe <jgg@ziepe.ca>,
Florian Fainelli <f.fainelli@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Russell King <linux@armlinux.org.uk>,
Chanwoo Choi <cw00.choi@samsung.com>,
Doug Ledford <dledford@redhat.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
linux-pci@vger.kernel.org, Darren Hart <dvhart@infradead.org>,
Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>,
Paul E. McKe
Subject: [PATCH 00/17] Address several documentation build warnings
Date: Tue, 17 Mar 2020 15:54:09 +0100 [thread overview]
Message-ID: <cover.1584456635.git.mchehab+huawei@kernel.org> (raw)
This patch series is against next-20200317. It addresses several warnings on
random places.
It is worth noticing patch 07/17: It changes kernel-doc parser to accept a
very common pattern on kernel-doc markups. This reduces a lot of
warnings all over the tree.
The remaining patches are just random fixes with the hope to address most
warnings that are shown in red when building the documentation.
Mauro Carvalho Chehab (17):
docs: amu: supress some Sphinx warnings
docs: arm64: booting.rst: get rid of some warnings
docs: pci: boot-interrupts.rst: improve html output
kernel: futex.c: get rid of a docs build warning
devfreq: devfreq.h: get rid of some doc warnings
firewire: firewire-cdev.hL get rid of a docs warning
scripts: kernel-doc: proper handle @foo->bar()
lib: bitmap.c: get rid of some doc warnings
rcu: update.c: get rid of some doc warnings
net: phy: sfp-bus.c: get rid of docs warnings
net: core: dev.c: fix a documentation warning
gpio: gpiolib.c: fix a doc warning
i2c: include/linux/i2c.h: fix a doc warning
infiniband: pa_vnic_encap.h: get rid of a warning
ata: libata-core: fix a doc warning
fs: inode.c: get rid of docs warnings
regulator: driver.h: fix regulator_map_* function names
Documentation/PCI/boot-interrupts.rst | 34 ++++++++++--------
Documentation/arm64/amu.rst | 5 +++
Documentation/arm64/booting.rst | 36 +++++++++++--------
drivers/ata/libata-core.c | 2 +-
drivers/gpio/gpiolib.c | 2 +-
.../infiniband/ulp/opa_vnic/opa_vnic_encap.h | 2 +-
drivers/net/phy/sfp-bus.c | 32 +++++++++--------
fs/inode.c | 6 ++--
include/linux/devfreq.h | 6 ++--
include/linux/i2c.h | 4 +--
include/linux/regulator/driver.h | 4 +--
include/uapi/linux/firewire-cdev.h | 2 +-
kernel/futex.c | 3 +-
kernel/rcu/update.c | 8 ++---
lib/bitmap.c | 27 +++++++-------
net/core/dev.c | 2 +-
scripts/kernel-doc | 2 ++
17 files changed, 101 insertions(+), 76 deletions(-)
--
2.24.1
next reply other threads:[~2020-03-17 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 14:54 Mauro Carvalho Chehab [this message]
2020-03-17 14:54 ` [PATCH 13/17] i2c: include/linux/i2c.h: fix a doc warning Mauro Carvalho Chehab
2020-03-17 15:03 ` Wolfram Sang
2020-03-17 15:05 ` Mauro Carvalho Chehab
2020-03-22 16:21 ` Wolfram Sang
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=cover.1584456635.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=andrew@lunn.ch \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=cw00.choi@samsung.com \
--cc=dledford@redhat.com \
--cc=dvhart@infradead.org \
--cc=f.fainelli@gmail.com \
--cc=jgg@ziepe.ca \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linux@armlinux.org.uk \
--cc=myungjoo.ham@samsung.com \
--cc=niranjana.vishwanathapura@intel.com \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
--cc=wsa@the-dreams.de \
/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).