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] A few late documentation updates
Date: Wed, 22 Nov 2017 09:31:20 -0700 [thread overview]
Message-ID: <20171122093120.0c7c4c11@lwn.net> (raw)
The following changes since commit
47427379ea80f1368ccec6ba20874fc19a9f0cc4:
documentation: fb: update list of available compiled-in fonts (2017-11-08 03:39:52 -0700)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-4.15-2
for you to fetch changes up to 3a025e1d1c2ea42fa497c9c6b21c284e0f69e28b:
Add optional check for bad kernel-doc comments (2017-11-20 12:09:11 -0700)
----------------------------------------------------------------
A few late-arriving docs updates that have no real reason to wait. There's
a new "Co-Developed-by" tag described by Greg, and a build enhancement from
Willy to generate docs warnings during a kernel build (but only when
additional warnings have been requested in general).
----------------------------------------------------------------
Greg Kroah-Hartman (1):
Documentation/process: add Co-Developed-by: tag for patches with multiple authors
Matthew Wilcox (1):
Add optional check for bad kernel-doc comments
Randy Dunlap (2):
documentation/svga.txt: update outdated file
Documentation: fix profile= options in kernel-parameters.txt
SeongJae Park (2):
kokr/memory-barriers/txt: Replace uses of "transitive"
kokr/memory-barriers.txt: Fix typo in paring example
Documentation/admin-guide/kernel-parameters.txt | 8 +-
Documentation/process/5.Posting.rst | 5 +
Documentation/svga.txt | 59 ++-----
.../translations/ko_KR/memory-barriers.txt | 178 ++++++++++-----------
scripts/Makefile.build | 5 +
scripts/kernel-doc | 25 ++-
6 files changed, 137 insertions(+), 143 deletions(-)
reply other threads:[~2017-11-22 16:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171122093120.0c7c4c11@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
all inboxes | Powered by JetHome®