All of lore.kernel.org
 help / color / mirror / Atom feed
From: Beatriz Martins de Carvalho <martinsdecarvalhobeatriz@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	outreachy-kernel@googlegroups.com
Subject: Re: [RESEND PATCH] staging: emxx_udc: Ending line with argument
Date: Wed, 7 Apr 2021 09:16:44 +0100	[thread overview]
Message-ID: <4d7ebe9c-8ebc-2fc9-10ed-6756ab42d5d7@gmail.com> (raw)
In-Reply-To: <YG1FI38zNbidjt9q@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]


Em 07/04/21 06:37, Greg KH escreveu:
> On Tue, Apr 06, 2021 at 09:00:07PM +0100, Beatriz Martins de Carvalho wrote:
>> Em 06/04/21 20:36, Greg KH escreveu:
>>> On Tue, Apr 06, 2021 at 08:34:09PM +0100, Beatriz Martins de Carvalho wrote:
>>>> Cleans up check of "Lines should not end with a '('"
>>>> with argument present in next line in file emxx_udc.c
>>>>
>>>> Signed-off-by: Beatriz Martins de Carvalho <martinsdecarvalhobeatriz@gmail.com>
>>>> ---
>>>>    drivers/staging/emxx_udc/emxx_udc.c | 11 ++++-------
>>>>    1 file changed, 4 insertions(+), 7 deletions(-)
>>> Why is this a [RESEND] ?
>>>
>>> What happened to the first version?
>> Sorry, I didn't receive your review, and in kernelnewbies tutorial, they say
>> if not receive a response, may have missed the patch, so I resent it.
> Do you have a pointer to your previous patch in the lore.kernel.org
> archives anywhere?  I can't seem to find it.


I found this, it's what is you need?

https://lore.kernel.org/linux-staging/20210401195457.24512-1-martinsdecarvalhobeatriz@gmail.com/

>
>>> Also, your subject is odd, please look at the documentation for how to
>>> write good subject lines for patches.
>> Yes, I know. It was my second patch, and I was learning, and when I resent
>> it, I didn't know if I can change the subject.
> Of course you can always fix up things you know you did incorrectly,
> don't make others review stuff that you know is wrong, that just wastes
> everyone's time.


Thank you, I will start to do this from now.

>
> thanks,
>
> greg k-h
Beatriz Martins de Carvalho

[-- Attachment #2: Type: text/html, Size: 3183 bytes --]

  reply	other threads:[~2021-04-07  8:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 19:34 [RESEND PATCH] staging: emxx_udc: Ending line with argument Beatriz Martins de Carvalho
2021-04-06 19:36 ` Greg KH
2021-04-06 20:00   ` Beatriz Martins de Carvalho
2021-04-07  5:37     ` Greg KH
2021-04-07  8:16       ` Beatriz Martins de Carvalho [this message]
2021-04-07  8:34         ` Greg KH
2021-04-07  9:46           ` Beatriz Martins de Carvalho
2021-04-07  9:54             ` Greg KH
2021-04-06 19:56 ` [Outreachy kernel] " Matthew Wilcox
2021-04-06 20:12   ` Beatriz Martins de Carvalho

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=4d7ebe9c-8ebc-2fc9-10ed-6756ab42d5d7@gmail.com \
    --to=martinsdecarvalhobeatriz@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.