From: Jason Gunthorpe <jgg@ziepe.ca>
To: Alessandro Ratti <alessandro@0x65c.net>
Cc: kevin.tian@intel.com, corbet@lwn.net, skhan@linuxfoundation.org,
iommu@lists.linux.dev, linux-doc@vger.kernel.org,
alessandro.ratti@gmail.com
Subject: Re: [PATCH] Documentation: fix spelling errors in iommufd.rst
Date: Mon, 18 Aug 2025 11:15:33 -0300 [thread overview]
Message-ID: <20250818141533.GF599331@ziepe.ca> (raw)
In-Reply-To: <20250815153840.188213-2-alessandro@0x65c.net>
On Fri, Aug 15, 2025 at 05:37:26PM +0200, Alessandro Ratti wrote:
> This patch corrects two minor spelling issues found in
> Documentation/userspace-api/iommufd.rst:
>
> - "primarly" -> "primarily"
> - "sharable" -> "shareable"
>
> Found using codespell(1).
>
> Signed-off-by: Alessandro Ratti <alessandro@0x65c.net>
> ---
> Documentation/userspace-api/iommufd.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
I'll pick this up to for-rc, thanks
Jason
prev parent reply other threads:[~2025-08-18 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 15:37 [PATCH] Documentation: fix spelling errors in iommufd.rst Alessandro Ratti
2025-08-15 15:37 ` Alessandro Ratti
2025-08-18 14:15 ` Jason Gunthorpe [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=20250818141533.GF599331@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=alessandro.ratti@gmail.com \
--cc=alessandro@0x65c.net \
--cc=corbet@lwn.net \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=linux-doc@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).