From 1efeca4e18fb084e21e8b1719953b076305ade3b Mon Sep 17 00:00:00 2001
From: qvkap <qvkapp@gmail.com>
Date: Tue, 18 Aug 2026 10:59:21 +0300
Subject: [PATCH] staging: most: fix typos in driver_usage.txt

Signed-off-by: qvkap <qvkapp@gmail.com>
---
 drivers/staging/most/Documentation/driver_usage.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/staging/most/Documentation/driver_usage.txt b/drivers/staging/most/Documentation/driver_usage.txt
index f1b6977f4..89ced829e 100644
--- a/drivers/staging/most/Documentation/driver_usage.txt
+++ b/drivers/staging/most/Documentation/driver_usage.txt
@@ -2,7 +2,7 @@
 		Section 1 Overview
 
 The Media Oriented Systems Transport (MOST) driver gives Linux applications
-access a MOST network: The Automotive Information Backbone and the de-facto
+access to a MOST network: The Automotive Information Backbone and the de-facto
 standard for high-bandwidth automotive multimedia networking.
 
 MOST defines the protocol, hardware and software layers necessary to allow
@@ -151,7 +151,7 @@ following attributes:
 	  pass parameters needed by some components
 	- create_link
 	  write '1' to this attribute to trigger the creation of the link. In
-	  case of speculative configuration, the creation is post-poned until
+	  case of speculative configuration, the creation is postponed until
 	  a physical device is being attached to the bus.
 	- destroy_link
 	  write '1' to this attribute to destroy an already established link
@@ -172,7 +172,7 @@ name in ALSA. The sound adapter will have the following attribute:
 	- create_card
 	  write '1' to this attribute to trigger the registration of the card
 	  with the ALSA subsystem.
-	  In case of speculative configuration, the creation is post-poned
+	  In case of speculative configuration, the creation is postponed
 	  until a physical device is being attached to the bus.
 
 Secondly, links will have to be created inside the adapter dir as described in
-- 
2.55.0

On Tue, Aug 18, 2026 at 01:22:12AM -0700, qvkap wrote:
> >From 1efeca4e18fb084e21e8b1719953b076305ade3b Mon Sep 17 00:00:00 2001
> From: qvkap <qvkapp@gmail.com>
> Date: Tue, 18 Aug 2026 10:59:21 +0300
> Subject: [PATCH] staging: most: fix typos in driver_usage.txt
> 
> Signed-off-by: qvkap <qvkapp@gmail.com>
> ---
>  drivers/staging/most/Documentation/driver_usage.txt | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- You did not specify a description of why the patch is needed, or
  possibly, any description at all, in the email body.  Please read the
  section entitled "The canonical patch format" in the kernel file,
  Documentation/process/submitting-patches.rst for what is needed in
  order to properly describe the change.

- It looks like you did not use your "real" name for the patch on either
  the Signed-off-by: line, or the From: line (both of which have to
  match).  Please read the kernel file,
  Documentation/process/submitting-patches.rst for how to do this
  correctly.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot