Re: [PATCH] staging: most: fix typo in driver_usage.txt

[Greg Kroah-Hartman <gregkh@linuxfoundation.org>]

On Tue, Oct 13, 2026 at 11:08:24AM +0800, wangyibo wrote:
> Fix a spelling mistake in the ALSA component description of the
> application layer section: 'can by used' should be 'can be used'.
> 
> The same typo was fixed for the networking and V4L2 sections by
> commit b114ef1efc49 ("staging: most: fix typos in driver_usage.txt"),
> but this third occurrence was missed.
> 
> Signed-off-by: wangyibo <szwyb123@gmail.com>
> ---
>  drivers/staging/most/Documentation/driver_usage.txt | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/most/Documentation/driver_usage.txt b/drivers/staging/most/Documentation/driver_usage.txt
> index f1b6977f4543..32a2e5ecb48b 100644
> --- a/drivers/staging/most/Documentation/driver_usage.txt
> +++ b/drivers/staging/most/Documentation/driver_usage.txt
> @@ -109,7 +109,7 @@ following components are available
>  	   driver via the V4L subsystem.
>  
>  	4) Advanced Linux Sound Architecture (ALSA)
> -	   Standard sound applications (e.g. aplay, arecord, audacity) can by
> +	   Standard sound applications (e.g. aplay, arecord, audacity) can be
>  	   used to access the driver via the ALSA subsystem.
>  
>  
> -- 
> 2.25.1
> 
> 

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:

- 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