linux-kernel - Re: Fixing Grammatical Error

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: <2024112255-grueling-glancing-2764@gregkh>
Date: Fri, 22 Nov 2024 00:44:19 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Vyshnav Ajith <puthen1977@...il.com>
Cc: corbet@....net, linux-usb@...r.kernel.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Fixing Grammatical Error

On Fri, Nov 22, 2024 at 05:08:29AM +0530, Vyshnav Ajith wrote:
> 'Worst case' being singular needs 'is' instead of 'are'.
> 
> Signed-off-by: Vyshnav Ajith <puthen1977@...il.com>
> ---
>  Documentation/usb/dwc3.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/usb/dwc3.rst b/Documentation/usb/dwc3.rst
> index f94a7ba16573..12989d126a8a 100644
> --- a/Documentation/usb/dwc3.rst
> +++ b/Documentation/usb/dwc3.rst
> @@ -20,7 +20,7 @@ Please pick something while reading :)
>      to the device. If MSI provides per-endpoint interrupt this dummy
>      interrupt chip can be replaced with "real" interrupts.
>    - interrupts are requested / allocated on usb_ep_enable() and removed on
> -    usb_ep_disable(). Worst case are 32 interrupts, the lower limit is two
> +    usb_ep_disable(). The worst case is 32 interrupts, the lower limit is two
>      for ep0/1.
>    - dwc3_send_gadget_ep_cmd() will sleep in wait_for_completion_timeout()
>      until the command completes.
> -- 
> 2.43.0
> 

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

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