From: Bjorn Helgaas <helgaas@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 1/2] Documentation: Fix typos
Date: Mon, 28 Jul 2025 17:23:47 -0500 [thread overview]
Message-ID: <20250728222347.GA3253635@bhelgaas> (raw)
In-Reply-To: <1412ff8c-50ff-4e51-b1c5-a4a404aafb86@infradead.org>
On Sat, Jul 26, 2025 at 08:16:26PM -0700, Randy Dunlap wrote:
> On 7/23/25 1:32 PM, Bjorn Helgaas wrote:
> > From: Bjorn Helgaas <bhelgaas@google.com>
> >
> > Fix typos.
> > Where more than one trigger may be specified that are comma deliminated.
> delimited.
Oof, thanks. Added to my local branch in case I repost.
> > -Note that irq domain lookups must happen in contexts that are
> > +Note that irq_domain lookups must happen in contexts that are
> > compatible with a RCU read-side critical section.
>
> an RCU
Thanks. 'git grep -i "\<a rcu"' says there are approximately a
zillion instances. I fixed this since it's next to another typo, but
not sure I have the energy to advocate for all the others :)
Bjorn
next prev parent reply other threads:[~2025-07-28 22:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 20:32 [PATCH 0/2] Documentation: Fix typos Bjorn Helgaas
2025-07-23 20:32 ` [PATCH 1/2] " Bjorn Helgaas
2025-07-27 3:16 ` Randy Dunlap
2025-07-28 22:23 ` Bjorn Helgaas [this message]
2025-07-29 0:25 ` Randy Dunlap
2025-07-23 20:32 ` [PATCH 2/2] Documentation/ABI: " Bjorn Helgaas
2025-07-26 4:02 ` Randy Dunlap
2025-08-11 17:22 ` [PATCH 0/2] Documentation: " Jonathan Corbet
-- strict thread matches above, loose matches on Subject: below --
2026-01-28 22:33 [PATCH 0/2] Fix grammar and example code in Documentation Patrick Little
2026-01-28 22:33 ` [PATCH 1/2] Documentation: Fix typos Patrick Little
2026-01-29 1:08 ` Randy Dunlap
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=20250728222347.GA3253635@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.