From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Khadija Kamran <kkamran.bese16seecs@seecs.edu.pk>,
outreachy@lists.linux.dev
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Khadija Kamran <kamrankhadijadj@gmail.com>
Subject: Re: [PATCH 0/4] staging: rtl8192e: code cleanup patches
Date: Thu, 23 Mar 2023 06:56:32 +0100 [thread overview]
Message-ID: <9cdfab96-ee7d-db11-4bde-71648a640385@gmail.com> (raw)
In-Reply-To: <cover.1679521517.git.kamrankhadijadj@gmail.com>
On 3/22/23 23:07, Khadija Kamran wrote:
> Fix several cleanup issues reported by checkpatch.pl in module
> staging/rtl8192e in file rtllib_rx.c
>
> Khadija Kamran (4):
> staging: rtl8192e: remove extra blank lines
> staging: rtl8192e: add blank lines after declarations
> staging: rtl8192e: add spaces around binary operators
> staging: rtl8192e: remove blank lines after '{'
>
> drivers/staging/rtl8192e/rtllib_rx.c | 73 +++++++++++-----------------
> 1 file changed, 29 insertions(+), 44 deletions(-)
>
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>'
Is this wanted?
Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>
next prev parent reply other threads:[~2023-03-23 5:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 22:07 [PATCH 0/4] staging: rtl8192e: code cleanup patches Khadija Kamran
2023-03-22 22:07 ` [PATCH 1/4] staging: rtl8192e: remove extra blank lines Khadija Kamran
2023-03-22 22:07 ` [PATCH 2/4] staging: rtl8192e: add blank lines after declarations Khadija Kamran
2023-03-22 22:07 ` [PATCH 3/4] staging: rtl8192e: add spaces around binary operators Khadija Kamran
2023-03-22 22:07 ` [PATCH 4/4] staging: rtl8192e: remove blank lines after '{' Khadija Kamran
2023-03-23 5:56 ` Philipp Hortmann [this message]
2023-03-23 12:04 ` [PATCH 0/4] staging: rtl8192e: code cleanup patches 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=9cdfab96-ee7d-db11-4bde-71648a640385@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kamrankhadijadj@gmail.com \
--cc=kkamran.bese16seecs@seecs.edu.pk \
--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;
as well as URLs for NNTP newsgroup(s).