From: Dixit Parmar <dixitparmar19@gmail.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Dixit Parmar <dixitparmar19@gmail.com>
Subject: [PATCH] docs: dt: submitting-patches: Fix typo
Date: Sat, 06 Sep 2025 14:47:45 +0530 [thread overview]
Message-ID: <20250906-doc-typo-fix-v1-1-74a427d3386f@gmail.com> (raw)
Fix trivial typo "serie" to "series".
Signed-off-by: Dixit Parmar <dixitparmar19@gmail.com>
---
Fix trivial typo "serie" to "series" in submitting-patches.rst.
---
Documentation/devicetree/bindings/submitting-patches.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/submitting-patches.rst b/Documentation/devicetree/bindings/submitting-patches.rst
index f3e23e69a638..97ae4f92d3dd 100644
--- a/Documentation/devicetree/bindings/submitting-patches.rst
+++ b/Documentation/devicetree/bindings/submitting-patches.rst
@@ -58,7 +58,7 @@ I. For patch submitters
any DTS patches, regardless whether using existing or new bindings, should
be placed at the end of patchset to indicate no dependency of drivers on
the DTS. DTS will be anyway applied through separate tree or branch, so
- different order would indicate the serie is non-bisectable.
+ different order would indicate the series is non-bisectable.
If a driver subsystem maintainer prefers to apply entire set, instead of
their relevant portion of patchset, please split the DTS patches into
---
base-commit: d7b8f8e20813f0179d8ef519541a3527e7661d3a
change-id: 20250906-doc-typo-fix-f430824427fb
Best regards,
--
Dixit Parmar <dixitparmar19@gmail.com>
next reply other threads:[~2025-09-06 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-06 9:17 Dixit Parmar [this message]
2025-09-06 11:56 ` [PATCH] docs: dt: submitting-patches: Fix typo Krzysztof Kozlowski
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=20250906-doc-typo-fix-v1-1-74a427d3386f@gmail.com \
--to=dixitparmar19@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).