linux-kernel - Re: [greybus-dev] [PATCH v3] Fix tiny typo in firmware-management docs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2025110200-announcer-handful-fc5d@gregkh>
Date: Sun, 2 Nov 2025 20:25:36 +0900
From: Greg KH <greg@...ah.com>
To: zntsproj <vacacax16@...il.com>
Cc: linux-kernel@...r.kernel.org, greybus-dev@...ts.linaro.org,
	zntsproj <vseokaktusah7@...il.com>
Subject: Re: [greybus-dev] [PATCH v3] Fix tiny typo in firmware-management
 docs

On Sat, Nov 01, 2025 at 10:52:47AM +0300, zntsproj wrote:
> Signed-off-by: zntsproj <vseokaktusah7@...il.com>
> ---
>  .../staging/greybus/Documentation/firmware/firmware-management  | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/greybus/Documentation/firmware/firmware-management b/drivers/staging/greybus/Documentation/firmware/firmware-management
> index 7918257e5..393455557 100644
> --- a/drivers/staging/greybus/Documentation/firmware/firmware-management
> +++ b/drivers/staging/greybus/Documentation/firmware/firmware-management
> @@ -193,7 +193,7 @@ Identifying the Character Device
>  
>  There can be multiple devices present in /dev/ directory with name
>  gb-authenticate-N and user first needs to identify the character device used for
> -authentication a of particular interface.
> +authentication of a particular interface.
>  
>  The Authentication core creates a device of class 'gb_authenticate', which shall
>  be used by the user to identify the right character device for it. The class
> -- 
> 2.51.2
> 
> _______________________________________________
> greybus-dev mailing list -- greybus-dev@...ts.linaro.org
> To unsubscribe send an email to greybus-dev-leave@...ts.linaro.org

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 sent multiple patches, yet no indication of which ones should be
  applied in which order.  Greg could just guess, but if you are
  receiving this email, he guessed wrong and the patches didn't apply.
  Please read the section entitled "The canonical patch format" in the
  kernel file, Documentation/process/submitting-patches.rst for a
  description of how to do this so that Greg has a chance to apply these
  correctly.

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

- You did not write a descriptive Subject: for the patch, allowing Greg,
  and everyone else, to know what this patch is all about.  Please read
  the section entitled "The canonical patch format" in the kernel file,
  Documentation/process/submitting-patches.rst for what a proper
  Subject: line should look like.

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

- This looks like a new version of a previously submitted patch, but you
  did not list below the --- line any changes from the previous version.
  Please read the section entitled "The canonical patch format" in the
  kernel file, Documentation/process/submitting-patches.rst for what
  needs to be done here to properly describe this.

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