From: Randy Dunlap <rdunlap@infradead.org>
To: Taimoor Zaeem <taimoorzaeem@gmail.com>,
andersson@kernel.org, "corbet@lwn.net" <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: staging: fix spelling error in remoteproc.rst
Date: Sun, 14 Sep 2025 10:03:50 -0700 [thread overview]
Message-ID: <5214509d-a2e6-4e55-823b-49f2dbfb5971@infradead.org> (raw)
In-Reply-To: <CANQcFN1s_iM8p5tYNz3Q_WyZki6Aw9_3HyoKwyoCVA9JeqG0eA@mail.gmail.com>
Hi--
On 9/14/25 4:46 AM, Taimoor Zaeem wrote:
>
(pasting email from
https://lore.kernel.org/linux-doc/CANQcFN1s_iM8p5tYNz3Q_WyZki6Aw9_3HyoKwyoCVA9JeqG0eA@mail.gmail.com/T/#u
)
From 10321c75f8fc1296775942f13cb3af78fdc8dcc8 Mon Sep 17 00:00:00 2001
From: Taimoor Zaeem <taimoorzaeem@gmail.com>
Date: Sun, 14 Sep 2025 16:31:56 +0500
Subject: [PATCH] Documentation: staging: fix spelling error in remoteproc.rst
Fix typo 'implementors' to 'implementers' in remote processor framework
documentation.
Signed-off-by: Taimoor Zaeem <taimoorzaeem@gmail.com>
---
Documentation/staging/remoteproc.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/staging/remoteproc.rst b/Documentation/staging/remoteproc.rst
index 348ee7e508ac..5c226fa076d6 100644
--- a/Documentation/staging/remoteproc.rst
+++ b/Documentation/staging/remoteproc.rst
@@ -104,7 +104,7 @@ Typical usage
rproc_shutdown(my_rproc);
}
-API for implementors
+API for implementers
====================
::
--
2.51.0
----------------- end of copy/paste --------------------
How do you know that's a typo?
Did you check on the internet to see if both spellings
are acceptable?
thanks.
--
~Randy
next prev parent reply other threads:[~2025-09-14 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 11:46 Taimoor Zaeem
2025-09-14 17:03 ` Randy Dunlap [this message]
2025-09-16 15:56 ` 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=5214509d-a2e6-4e55-823b-49f2dbfb5971@infradead.org \
--to=rdunlap@infradead.org \
--cc=andersson@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=taimoorzaeem@gmail.com \
/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®