linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: [GIT PULL] Documentation fixes
Date: Fri, 8 Jan 2021 10:31:20 -0700	[thread overview]
Message-ID: <20210108103120.73a35ba6@lwn.net> (raw)

The following changes since commit
5c8fe583cce542aa0b84adc939ce85293de36e5e:

  Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)

are available in the Git repository at:

  git://git.lwn.net/linux.git tags/docs-5.11-3

for you to fetch changes up to 9d54ee78aef62c29b15ae2f58a70b1d1cd63a8f0:

  docs: admin-guide: bootconfig: Fix feils to fails (2021-01-07 14:44:58 -0700)

----------------------------------------------------------------
A handful of relatively small documentation fixes.

----------------------------------------------------------------
Bhaskar Chowdhury (1):
      docs: admin-guide: bootconfig: Fix feils to fails

Jonathan Neuschäfer (1):
      docs: binfmt-misc: Fix .rst formatting

Liao Pingfang (1):
      docs/mm: concepts.rst: Correct the threshold to low watermark

Lukas Bulwahn (1):
      atomic: remove further references to atomic_ops

Miguel Ojeda (1):
      docs: remove mention of ENABLE_MUST_CHECK

Nícolas F. R. A. Prado (1):
      docs: Fix reST markup when linking to sections

Randy Dunlap (3):
      Documentation: admin: early_param()s are also listed in kernel-parameters
      Documentation: doc-guide: fixes to sphinx.rst
      Documentation/admin-guide: kernel-parameters: hyphenate comma-separated

 .../Memory-Ordering/Tree-RCU-Memory-Ordering.rst   |  8 +++---
 .../RCU/Design/Requirements/Requirements.rst       | 20 +++++++-------
 Documentation/admin-guide/binfmt-misc.rst          |  4 +--
 Documentation/admin-guide/bootconfig.rst           |  2 +-
 Documentation/admin-guide/kernel-parameters.rst    |  4 +--
 Documentation/admin-guide/kernel-parameters.txt    | 12 ++++----
 Documentation/admin-guide/mm/concepts.rst          |  2 +-
 Documentation/core-api/index.rst                   |  1 -
 Documentation/doc-guide/sphinx.rst                 | 32 +++++++++++-----------
 Documentation/kernel-hacking/locking.rst           |  8 +++---
 Documentation/process/4.Coding.rst                 |  6 ++--
 .../sound/kernel-api/writing-an-alsa-driver.rst    | 16 +++++------
 MAINTAINERS                                        |  1 -
 13 files changed, 56 insertions(+), 60 deletions(-)

             reply	other threads:[~2021-01-08 17:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 17:31 Jonathan Corbet [this message]
2021-01-09  1:21 ` [GIT PULL] Documentation fixes pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2024-01-26 16:04 Jonathan Corbet
2024-01-26 23:22 ` pr-tracker-bot
2022-10-13 16:41 Jonathan Corbet
2022-10-13 18:00 ` pr-tracker-bot
2022-01-21 14:49 Jonathan Corbet
2022-01-22  8:06 ` pr-tracker-bot
2021-05-12 20:49 Jonathan Corbet
2021-05-12 22:48 ` pr-tracker-bot
2020-08-31 19:10 Jonathan Corbet
2020-08-31 19:48 ` pr-tracker-bot
2020-04-10 16:23 Jonathan Corbet
2020-04-11  1:20 ` pr-tracker-bot
2019-01-04 22:02 Jonathan Corbet
2019-01-06  2:40 ` pr-tracker-bot

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=20210108103120.73a35ba6@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;
as well as URLs for NNTP newsgroup(s).