mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Documentation fixes for 6.8
Date: Wed, 17 Jan 2024 09:29:40 -0700	[thread overview]
Message-ID: <87h6jb6hzf.fsf@meer.lwn.net> (raw)

The following changes since commit 2d179e8ac02e33c82c1a314961254353eb5028b3:

  MAINTAINERS: use tabs for indent of CONFIDENTIAL COMPUTING THREAT MODEL (2024-01-08 11:39:00 -0700)

are available in the Git repository at:

  git://git.lwn.net/linux.git tags/docs-6.8-2

for you to fetch changes up to ead8467f96d6dc35bbf8c63ee9d244a357ede84a:

  docs, kprobes: Add loongarch as supported architecture (2024-01-11 09:36:37 -0700)

----------------------------------------------------------------
A handful of late-arriving documentation fixes.

----------------------------------------------------------------
Baruch Siach (1):
      docs: admin-guide: hw_random: update rng-tools website

Tiezhu Yang (2):
      docs, kprobes: Update email address of Masami Hiramatsu
      docs, kprobes: Add loongarch as supported architecture

Vegard Nossum (2):
      Documentation: constrain alabaster package to older versions
      docs: kernel_feat.py: fix potential command injection

attreyee-muk (1):
      Documentation/core-api: fix spelling mistake in workqueue

 Documentation/admin-guide/features.rst             |  2 +-
 Documentation/admin-guide/hw_random.rst            |  5 +-
 Documentation/arch/arc/features.rst                |  2 +-
 Documentation/arch/arm/features.rst                |  2 +-
 Documentation/arch/arm64/features.rst              |  2 +-
 Documentation/arch/loongarch/features.rst          |  2 +-
 Documentation/arch/m68k/features.rst               |  2 +-
 Documentation/arch/mips/features.rst               |  2 +-
 Documentation/arch/nios2/features.rst              |  2 +-
 Documentation/arch/openrisc/features.rst           |  2 +-
 Documentation/arch/parisc/features.rst             |  2 +-
 Documentation/arch/powerpc/features.rst            |  2 +-
 Documentation/arch/riscv/features.rst              |  2 +-
 Documentation/arch/s390/features.rst               |  2 +-
 Documentation/arch/sh/features.rst                 |  2 +-
 Documentation/arch/sparc/features.rst              |  2 +-
 Documentation/arch/x86/features.rst                |  2 +-
 Documentation/arch/xtensa/features.rst             |  2 +-
 Documentation/core-api/workqueue.rst               |  2 +-
 Documentation/sphinx/kernel_feat.py                | 55 +++++-----------------
 Documentation/sphinx/requirements.txt              |  2 +
 Documentation/trace/kprobes.rst                    |  3 +-
 .../translations/zh_CN/arch/loongarch/features.rst |  2 +-
 .../translations/zh_CN/arch/mips/features.rst      |  2 +-
 .../translations/zh_TW/arch/loongarch/features.rst |  2 +-
 .../translations/zh_TW/arch/mips/features.rst      |  2 +-
 26 files changed, 39 insertions(+), 70 deletions(-)

             reply	other threads:[~2024-01-17 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 16:29 Jonathan Corbet [this message]
2024-01-17 20:03 ` 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=87h6jb6hzf.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linuxfoundation.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®