The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sukrut Heroorkar <hsukrut3@gmail.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: skhan@linuxfoundation.org, Sukrut Heroorkar <hsukrut3@gmail.com>
Subject: [PATCH] Documentation/devicetree: Fixing a typo in usuage-model.rst
Date: Sat, 17 May 2025 16:40:20 +0200	[thread overview]
Message-ID: <20250517144020.870706-1-hsukrut3@gmail.com> (raw)

Fixes a minor spelling issue by correcting "busses" to the correct plural form "buses".

Signed-off-by: Sukurt Heroorkar <hsukrut3@gmail.com>
---
 Documentation/devicetree/usage-model.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/devicetree/usage-model.rst b/Documentation/devicetree/usage-model.rst
index 0717426856b2..6f9a2c0a380a 100644
--- a/Documentation/devicetree/usage-model.rst
+++ b/Documentation/devicetree/usage-model.rst
@@ -27,7 +27,7 @@ links from one node to another outside of the natural tree structure.
 
 Conceptually, a common set of usage conventions, called 'bindings',
 is defined for how data should appear in the tree to describe typical
-hardware characteristics including data busses, interrupt lines, GPIO
+hardware characteristics including data buses, interrupt lines, GPIO
 connections, and peripheral devices.
 
 As much as possible, hardware is described using existing bindings to
@@ -36,7 +36,7 @@ names are simply text strings, it is easy to extend existing bindings
 or create new ones by defining new nodes and properties.  Be wary,
 however, of creating a new binding without first doing some homework
 about what already exists.  There are currently two different,
-incompatible, bindings for i2c busses that came about because the new
+incompatible, bindings for i2c buses that came about because the new
 binding was created without first investigating how i2c devices were
 already being enumerated in existing systems.
 
-- 
2.43.0


             reply	other threads:[~2025-05-17 14:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-17 14:40 Sukrut Heroorkar [this message]
2025-05-19 16:38 ` [PATCH] Documentation/devicetree: Fixing a typo in usuage-model.rst Conor Dooley

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=20250517144020.870706-1-hsukrut3@gmail.com \
    --to=hsukrut3@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 \
    --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