From: Alison Schofield <alison.schofield@intel.com>
To: Ayush Tiwari <ayushtiw0110@gmail.com>
Cc: Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-staging@lists.linux.dev, outreachy@lists.linux.dev
Subject: Re: [PATCH v3 0/3] Trivial code cleanup patches
Date: Fri, 22 Mar 2024 20:31:22 -0700 [thread overview]
Message-ID: <Zf5NCuZ/JNbcSpky@aschofie-mobl2> (raw)
In-Reply-To: <cover.1710965653.git.ayushtiw0110@gmail.com>
On Thu, Mar 21, 2024 at 02:55:07AM +0530, Ayush Tiwari wrote:
> Address different kinds of checkpatch complains for the rtl8712 module
> to ensure adherence to coding style guidelines.
Thanks for sending v3 as a new email, rather than threaded with
prior revisions.
I think you repeat the changelog in the patches, but I'll go
ahead and comment right here. It applies in the patch too.
>
> Changes in v3: Fixed issues about backupPMKIDList and verified with
> CONFIG_WERROR set and built the kernel.
>
> Changes in v2: Checked any possible reuse of backup_PMKID_list
> manually and rebuilt, rebooted the kernel and loaded the driver
> with modprobe.
The change log is to inform reviewers of what actually changed
in the patch since previous version. So let's be specific
in these v2, v3, and next a v4 changelog. I think this is
right:
v4: Update the changelog to match revision history
v3: Update memcpy() param to match new name backup_PMKID_list
v2: No changes. Just a patch sending error.
There's a section in the first patch tutorial about replying to
patch feedback and you can read any of the lore lists to see
examples. Folks will expect you to reply to their feedback.
Even if it's just a simple "Thanks, got it!" Then, they will
look to see if their feedback affected the next revision.
--Alison
>
> Ayush Tiwari (3):
> staging: rtl8712: rename backupPMKIDList to backup_PMKID_list
> staging: rtl8712: rename backupPMKIDIndex to backup_PMKID_index
> staging: rtl8712: rename backupTKIPCountermeasure to
> backup_TKIP_countermeasure
>
> drivers/staging/rtl8712/mlme_linux.c | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
>
> --
> 2.40.1
>
>
next prev parent reply other threads:[~2024-03-23 3:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 21:14 [PATCH v3 0/3] Trivial code cleanup patches Ayush Tiwari
2024-03-20 21:19 ` [PATCH v3 1/3] staging: rtl8712: rename backupPMKIDList to backup_PMKID_list Ayush Tiwari
2024-03-24 20:49 ` [PATCH v4 " Ayush Tiwari
2024-03-20 21:20 ` [PATCH v3 2/3] staging: rtl8712: rename backupPMKIDIndex to backup_PMKID_index Ayush Tiwari
2024-03-24 20:51 ` [PATCH v4 " Ayush Tiwari
2024-03-20 21:21 ` [PATCH v3 3/3] staging: rtl8712: rename backupTKIPCountermeasure to backup_TKIP_countermeasure Ayush Tiwari
2024-03-24 20:52 ` [PATCH v4 " Ayush Tiwari
2024-03-20 21:25 ` [PATCH v3 0/3] Trivial code cleanup patches Ayush Tiwari
2024-03-23 3:31 ` Alison Schofield [this message]
2024-03-24 20:47 ` [PATCH v4 " Ayush Tiwari
2024-03-25 17:23 ` [PATCH v3 " Greg KH
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=Zf5NCuZ/JNbcSpky@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=Larry.Finger@lwfinger.net \
--cc=ayushtiw0110@gmail.com \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--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