From: Jonathan Corbet <corbet@lwn.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-doc@vger.kernel.org
Subject: [PULL] Documentation fixes
Date: Mon, 4 Dec 2017 14:52:27 -0700 [thread overview]
Message-ID: <20171204145227.37446d63@lwn.net> (raw)
The following changes since commit
4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-4.15-fixes
for you to fetch changes up to 9956cfef3409177d9e24ea4b7910148a18073a6f:
Documentation: fix docs build error after source file removed (2017-12-03 15:11:45 -0700)
----------------------------------------------------------------
A handful of documentation fixes. The most significant of these addresses
a problem with the new warning mode: it can break the build when confronted
with a source file containing malformed kerneldoc comments.
----------------------------------------------------------------
John Pittman (1):
scsi: documentation: Fix case of 'scsi_device' struct mention(s)
Jonathan Neuschäfer (1):
genericirq.rst: Remove :c:func:`...` in code blocks
Masanari Iida (1):
dmaengine: doc : Fix warning "Title underline too short" while make xmldocs
Randy Dunlap (1):
Documentation: fix docs build error after source file removed
Will Deacon (1):
scripts/kernel-doc: Don't fail with status != 0 if error encountered with -none
Documentation/core-api/genericirq.rst | 16 ++++++++--------
Documentation/driver-api/dmaengine/client.rst | 2 +-
Documentation/driver-api/pci.rst | 3 ---
Documentation/scsi/scsi_mid_low_api.txt | 6 +++---
scripts/kernel-doc | 2 +-
5 files changed, 13 insertions(+), 16 deletions(-)
next reply other threads:[~2017-12-04 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 21:52 Jonathan Corbet [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-13 16:35 [PULL] Documentation fixes Jonathan Corbet
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=20171204145227.37446d63@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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