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: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [GIT PULL] Documentation fixes
Date: Wed, 12 May 2021 14:49:58 -0600	[thread overview]
Message-ID: <87mtszad8p.fsf@meer.lwn.net> (raw)

The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:

  Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 7240cd200541543008a7ce4fcaf2ba5a5556128f:

  Remove link to nonexistent rocket driver docs (2021-05-11 11:02:39 -0600)

----------------------------------------------------------------
A set of straightforward documentation fixes.

----------------------------------------------------------------
Desmond Cheong Zhi Xi (1):
      Remove link to nonexistent rocket driver docs

Mauro Carvalho Chehab (5):
      docs: cdrom-standard.rst: get rid of uneeded UTF-8 chars
      docs: ABI: remove a meaningless UTF-8 character
      docs: ABI: remove some spurious characters
      docs: hwmon: tmp103.rst: fix bad usage of UTF-8 chars
      docs: networking: device_drivers: fix bad usage of UTF-8 chars

Randy Dunlap (1):
      Documentation: drop optional BOMs

Wan Jiabing (1):
      docs/zh_CN: Remove obsolete translation file

 .../ABI/obsolete/sysfs-kernel-fadump_registered    |  2 +-
 .../ABI/obsolete/sysfs-kernel-fadump_release_mem   |  2 +-
 Documentation/ABI/testing/sysfs-module             |  4 +-
 Documentation/block/data-integrity.rst             |  2 +-
 Documentation/cdrom/cdrom-standard.rst             | 30 ++++++-------
 Documentation/driver-api/serial/index.rst          |  1 -
 Documentation/hwmon/tmp103.rst                     |  4 +-
 .../device_drivers/ethernet/intel/i40e.rst         |  4 +-
 .../device_drivers/ethernet/intel/iavf.rst         |  2 +-
 .../process/kernel-enforcement-statement.rst       |  2 +-
 Documentation/security/tpm/xen-tpmfront.rst        |  2 +-
 Documentation/timers/no_hz.rst                     |  2 +-
 Documentation/translations/zh_CN/SecurityBugs      | 50 ----------------------
 Documentation/usb/mtouchusb.rst                    |  2 +-
 Documentation/usb/usb-serial.rst                   |  2 +-
 15 files changed, 30 insertions(+), 81 deletions(-)
 delete mode 100644 Documentation/translations/zh_CN/SecurityBugs

             reply	other threads:[~2021-05-12 20:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 20:49 Jonathan Corbet [this message]
2021-05-12 22:48 ` [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-01-08 17:31 Jonathan Corbet
2021-01-09  1:21 ` 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=87mtszad8p.fsf@meer.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).