From: Dan Carpenter <error27@gmail.com>
To: Khadija Kamran <kamrankhadijadj@gmail.com>
Cc: Julia Lawall <julia.lawall@inria.fr>,
outreachy@lists.linux.dev, gregkh@linuxfoundation.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH 0/4] staging: rtl8192e: code cleanup patches
Date: Thu, 23 Mar 2023 18:32:54 +0300 [thread overview]
Message-ID: <1973548d-e76e-4512-bed4-792c95b59c12@kili.mountain> (raw)
In-Reply-To: <ZBxu5RBG9kCRlwRB@khadija-virtual-machine>
On Thu, Mar 23, 2023 at 08:23:17PM +0500, Khadija Kamran wrote:
> On Thu, Mar 23, 2023 at 04:34:43PM +0300, Dan Carpenter wrote:
> > On Thu, Mar 23, 2023 at 02:08:58PM +0100, Julia Lawall wrote:
> > >
> > >
> > > On Thu, 23 Mar 2023, Julia Lawall wrote:
> > >
> > > >
> > > >
> > > > On Thu, 23 Mar 2023, Khadija Kamran wrote:
> > > >
> > > > > Fix several cleanup issues reported by checkpatch.pl in module
> > > > > staging/rtl8192e in file rtllib_rx.c
> > > >
> > > > Why is it resent?
> > >
> > > OK, I see, sorry for the noise.
> >
> > I'm still confused... :P
> >
>
> Hey Dan!
>
> Sorry about the confusion. I sent the last patch with the wrong email
> mistakenly. It was causing following warning as reported by Philipp,
> Checkpatch:
>
> WARNING: From:/Signed-off-by: email address mismatch: 'From: Khadija
> Kamran <kkamran.bese16seecs@seecs.edu.pk>' != 'Signed-off-by: Khadija
> Kamran <kamrankhadijadj@gmail.com>
>
> I resent this patch with the correct email address. I hope I did not do
> this wrong.
It needs to be v2: resend from the correct email address.
When you send a patch a second time that always needs to be explained
because we don't remember all the email we get. The v2 information is
really interesting as a reviewer. Maybe I am wondering, "Did I respond
to the original email and is my complaint fixed?"
For RESEND patches it means that the first patch was perfect but
something broke down in the process. Maybe a maintainer was on vacation
and accidentally ignored the patch. If Greg asks you to resend
everything that's a kind of breakdown in the process as well, but just
add that information in the patch "Resending all the most/ patches
because it was confusing which one were supposed to be applied".
That information is super interesting because it shows we are all on the
same page about how to go forward.
regards,
dan carpenter
next prev parent reply other threads:[~2023-03-23 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 12:41 Khadija Kamran
2023-03-23 12:41 ` [RESEND PATCH 1/4] staging: rtl8192e: remove extra blank lines Khadija Kamran
2023-03-23 12:41 ` [RESEND PATCH 2/4] staging: rtl8192e: add blank lines after declarations Khadija Kamran
2023-03-23 12:41 ` [RESEND PATCH 3/4] staging: rtl8192e: add spaces around binary operators Khadija Kamran
2023-03-23 12:41 ` [RESEND PATCH 4/4] staging: rtl8192e: remove blank lines after '{' Khadija Kamran
2023-03-23 13:08 ` [RESEND PATCH 0/4] staging: rtl8192e: code cleanup patches Julia Lawall
2023-03-23 13:08 ` Julia Lawall
2023-03-23 13:34 ` Dan Carpenter
2023-03-23 15:23 ` Khadija Kamran
2023-03-23 15:27 ` Greg KH
2023-03-23 15:32 ` Dan Carpenter [this message]
2023-03-23 19:30 ` Khadija Kamran
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=1973548d-e76e-4512-bed4-792c95b59c12@kili.mountain \
--to=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=kamrankhadijadj@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
/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
all inboxes | Powered by JetHome®