From: Greg KH <gregkh@linuxfoundation.org>
To: Jilin Yuan <yuanjilin@cdjrlc.com>
Cc: daniel@zonque.org, haojian.zhuang@gmail.com,
robert.jarzmik@free.fr, balbi@kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gadget/udc: fix repeated words in comments
Date: Mon, 22 Aug 2022 08:14:25 +0200 [thread overview]
Message-ID: <YwMewdmmxiFdbXV1@kroah.com> (raw)
In-Reply-To: <20220821152009.61380-1-yuanjilin@cdjrlc.com>
On Sun, Aug 21, 2022 at 11:20:09PM +0800, Jilin Yuan wrote:
> Delete the redundant word 'tell'.
>
> Signed-off-by: Jilin Yuan <yuanjilin@cdjrlc.com>
> ---
> drivers/usb/gadget/udc/pxa25x_udc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/gadget/udc/pxa25x_udc.c b/drivers/usb/gadget/udc/pxa25x_udc.c
> index c593fc383481..176e2b157021 100644
> --- a/drivers/usb/gadget/udc/pxa25x_udc.c
> +++ b/drivers/usb/gadget/udc/pxa25x_udc.c
> @@ -1737,7 +1737,7 @@ static void handle_ep0 (struct pxa25x_udc *dev)
> /* hardware automagic preventing STALL... */
> if (dev->req_config) {
> /* hardware sometimes neglects to tell
> - * tell us about config change events,
> + * us about config change events,
> * so later ones may fail...
> */
> WARNING("config change %02x fail %d?\n",
> --
> 2.36.1
>
You sent 3 patches that do different things, yet have the same exact
subject line :(
Please fix up and resend _ALL_ of your USB patches with a unique subject
line, _AND_ as a patch series as I have now dropped them all from my
review queue.
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-22 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 15:20 [PATCH] gadget/udc: fix repeated words in comments Jilin Yuan
2022-08-22 6:14 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-21 15:22 Jilin Yuan
2022-08-21 15:24 Jilin Yuan
2022-08-22 11:57 Jilin Yuan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YwMewdmmxiFdbXV1@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=balbi@kernel.org \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
--cc=yuanjilin@cdjrlc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox