[PATCH] Documentation/devicetree: Fixing a typo in usuage-model.rst

[PATCH] Documentation/devicetree: Fixing a typo in usuage-model.rst

[Sukrut Heroorkar]

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

Re: [PATCH] Documentation/devicetree: Fixing a typo in usuage-model.rst

[Conor Dooley]

[-- Attachment #1: Type: text/plain, Size: 1784 bytes --]

On Sat, May 17, 2025 at 04:40:20PM +0200, Sukrut Heroorkar wrote:
> Fixes a minor spelling issue by correcting "busses" to the correct plural form "buses".

I think those are maybe valid us-english spellings of the word, and your
subject has a typo.

> 
> 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
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]