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-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [GIT PULL] Documentation stragglers for 7.3
Date: Wed, 26 Aug 2026 10:23:05 -0600	[thread overview]
Message-ID: <877blcsvfa.fsf@trenco.lwn.net> (raw)

The following changes since commit 791e420360669d55b7f90ca0c6d61b10e4992aec:

  Doc: admin-guide: pm: Remove unnecessary backticks and fix a spell (2026-08-14 12:36:43 -0600)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/docs/linux.git tags/docs-7.3-2

for you to fetch changes up to 94509f50d696bff745fe26457ce421cea8525bee:

  docs: panic: Disclaimer about console verbosity when using panic_print with pstore (2026-08-24 11:12:29 -0600)

----------------------------------------------------------------
A handful of late-arriving fixes, a Japanese translation that was ready
long ago but fell through the cracks, and an update to the Italian
translations.

----------------------------------------------------------------
Akiyoshi Kurita (1):
      docs/ja_JP: translate submitting-patches.rst (tag usage)

Federico Vaga (1):
      doc:it_IT: align Italian documentation in process

Guilherme G. Piccoli (1):
      docs: panic: Disclaimer about console verbosity when using panic_print with pstore

Jenson Johnathon Reggentin (1):
      docs: block: fix dead http link in blk-mq.rst

Johan Hovold (1):
      docs: threat-model: fix /dev/kmsg reference

Randy Dunlap (1):
      docs: kernel-parameters: add CPU_FREQ, CPU_IDLE build options

 Documentation/admin-guide/kernel-parameters.txt    |  21 +-
 Documentation/block/blk-mq.rst                     |   2 +-
 Documentation/process/threat-model.rst             |   2 +-
 .../translations/it_IT/process/1.Intro.rst         |  14 +-
 .../translations/it_IT/process/2.Process.rst       |  59 +++---
 .../translations/it_IT/process/5.Posting.rst       |  34 +++-
 .../it_IT/process/7.AdvancedTopics.rst             |   2 +-
 .../translations/it_IT/process/adding-syscalls.rst |  94 +++++++++
 .../translations/it_IT/process/coding-style.rst    |  33 ++--
 .../translations/it_IT/process/deprecated.rst      |  85 ++++++--
 .../translations/it_IT/process/email-clients.rst   |   9 +-
 Documentation/translations/it_IT/process/index.rst |   8 +
 .../translations/it_IT/process/license-rules.rst   |  16 +-
 .../it_IT/process/maintainer-handbooks.rst         |  15 +-
 .../it_IT/process/maintainer-pgp-guide.rst         | 172 +++++++++--------
 .../translations/it_IT/process/maintainers.rst     |   2 +
 .../it_IT/process/programming-language.rst         |   6 +-
 .../it_IT/process/submit-checklist.rst             |   9 +-
 .../it_IT/process/submitting-patches.rst           | 214 ++++++++++++++-------
 .../ja_JP/process/submitting-patches.rst           |  94 +++++++++
 20 files changed, 635 insertions(+), 256 deletions(-)

             reply	other threads:[~2026-08-26 16:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 16:23 Jonathan Corbet [this message]
2026-08-26 18:39 ` 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=877blcsvfa.fsf@trenco.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®