From: Alexander Shatalin <sashatalin03@gmail.com>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Shatalin <sashatalin03@gmail.com>
Subject: [PATCH] docs: fix typo in firmware-related section
Date: Wed, 30 Apr 2025 14:27:26 +0000 [thread overview]
Message-ID: <20250430142726.3276-1-sashatalin03@gmail.com> (raw)
Fix a minor grammar issue by changing 'firmwares' to 'firmware' in the
Documentation/index.rst file.
Signed-off-by: Alexander Shatalin <sashatalin03@gmail.com>
---
Documentation/index.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/index.rst b/Documentation/index.rst
index f9f525f4c0dd..c0cf79a87c3a 100644
--- a/Documentation/index.rst
+++ b/Documentation/index.rst
@@ -84,7 +84,7 @@ which are kept separately from the kernel's own documentation.
Firmware-related documentation
==============================
The following holds information on the kernel's expectations regarding the
-platform firmwares.
+platform firmware.
.. toctree::
:maxdepth: 1
--
2.34.1
next reply other threads:[~2025-04-30 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 14:27 Alexander Shatalin [this message]
2025-05-06 13:08 ` [PATCH] docs: fix typo in firmware-related section 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=20250430142726.3276-1-sashatalin03@gmail.com \
--to=sashatalin03@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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