From: Jonathan Corbet <corbet@lwn.net>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 0/9] Documentation: Fix typos
Date: Mon, 18 Aug 2025 10:44:26 -0600 [thread overview]
Message-ID: <87frdo8tqt.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250813200526.290420-1-helgaas@kernel.org>
Bjorn Helgaas <helgaas@kernel.org> writes:
> From: Bjorn Helgaas <bhelgaas@google.com>
>
> Fix typos in Documentation/. Based on v6.17-rc1.
>
> "git log -p --word-diff" or similar might make this easier to review.
>
> Feel free drop any conflicts; nothing here touches code or messages.
>
> Bjorn Helgaas (9):
> Documentation: Fix PCI typos
> Documentation: Fix RCU typos
> Documentation: Fix admin-guide typos
> Documentation: Fix core-api typos
> Documentation: Fix filesystems typos
> Documentation: Fix networking typos
> Documentation: Fix power typos
> Documentation: Fix trace typos
> Documentation: Fix misc typos
That last patch conflicts with linux-next, so I've dropped it; the rest
are applied.
Thanks,
jon
prev parent reply other threads:[~2025-08-18 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 20:04 Bjorn Helgaas
2025-08-13 20:04 ` [PATCH 1/9] Documentation: Fix PCI typos Bjorn Helgaas
2025-08-13 20:04 ` [PATCH 2/9] Documentation: Fix RCU typos Bjorn Helgaas
2025-08-13 20:04 ` [PATCH 3/9] Documentation: Fix admin-guide typos Bjorn Helgaas
2025-08-13 20:05 ` [PATCH 4/9] Documentation: Fix core-api typos Bjorn Helgaas
2025-08-13 20:05 ` [PATCH 5/9] Documentation: Fix filesystems typos Bjorn Helgaas
2025-08-13 20:05 ` [PATCH 6/9] Documentation: Fix networking typos Bjorn Helgaas
2025-08-13 20:05 ` [PATCH 7/9] Documentation: Fix power typos Bjorn Helgaas
2025-08-13 20:05 ` [PATCH 8/9] Documentation: Fix trace typos Bjorn Helgaas
2025-08-13 20:05 ` [PATCH 9/9] Documentation: Fix misc typos Bjorn Helgaas
2025-08-18 16:44 ` Jonathan Corbet [this message]
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=87frdo8tqt.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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®