public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: Kit Dallege <xaum.io@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH v2 0/3] docs: assorted documentation fixes
Date: Sun, 15 Mar 2026 18:05:18 +0100	[thread overview]
Message-ID: <20260315170521.63794-1-xaum.io@gmail.com> (raw)

Three independent doc fixes: a stale file path in the kernel-doc guide,
misleading wording in sched-stats, and minor grammar issues in the
development process guide.

Changes in v2:
- Fix Assisted-by tag format per Documentation/process/coding-assistants.rst
  (Randy Dunlap)

Kit Dallege (3):
  docs: kernel-doc: fix stale intel_audio.c path in examples
  docs: sched-stats: fix misleading 'per-process' wording
  docs: process: fix grammatical errors in 2.Process.rst

 Documentation/doc-guide/kernel-doc.rst                 |  4 ++--
 Documentation/process/2.Process.rst                    | 10 +++++-----
 Documentation/scheduler/sched-stats.rst                |  4 ++--
 .../translations/it_IT/doc-guide/kernel-doc.rst        |  4 ++--
 .../translations/zh_CN/doc-guide/kernel-doc.rst        |  4 ++--
 5 files changed, 13 insertions(+), 13 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-03-15 17:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-15 17:05 Kit Dallege [this message]
2026-03-15 17:05 ` [PATCH v2 1/3] docs: kernel-doc: fix stale intel_audio.c path in examples Kit Dallege
2026-03-15 17:05 ` [PATCH v2 2/3] docs: sched-stats: fix misleading 'per-process' wording Kit Dallege
2026-03-16 13:44   ` Jonathan Corbet
2026-03-15 17:05 ` [PATCH v2 3/3] docs: process: fix grammatical errors in 2.Process.rst Kit Dallege
2026-03-16 13:43   ` Jonathan Corbet

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=20260315170521.63794-1-xaum.io@gmail.com \
    --to=xaum.io@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@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