From: Jeremy Kerr <jk@ozlabs.org>
To: Randy Dunlap <rdunlap@infradead.org>, linux-doc@vger.kernel.org
Cc: linuxppc-dev@lists.ozlabs.org, Arnd Bergmann <arnd@arndb.de>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation: spufs: correct a duplicate word typo
Date: Tue, 30 Aug 2022 07:40:28 +0800 [thread overview]
Message-ID: <bc95ca95965e69aa434454b5f9fd02c378e35b1e.camel@ozlabs.org> (raw)
In-Reply-To: <20220829232908.32437-1-rdunlap@infradead.org>
Hi Randy,
> Fix a typo of "or" which should be "of".
Nice, people are still reading the spufs docs! :D
Looks good to me, thanks for the patch.
Reviewed-by: Jeremy Kerr <jk@ozlabs.org>
Cheers,
Jeremy
next prev parent reply other threads:[~2022-08-29 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 23:29 [PATCH] Documentation: spufs: correct a duplicate word typo Randy Dunlap
2022-08-29 23:40 ` Jeremy Kerr [this message]
2022-09-21 20:10 ` 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=bc95ca95965e69aa434454b5f9fd02c378e35b1e.camel@ozlabs.org \
--to=jk@ozlabs.org \
--cc=arnd@arndb.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).