From: Greg KH <gregkh@linuxfoundation.org>
To: Ayush Tiwari <ayushtiw0110@gmail.com>
Cc: Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH v3 0/3] Trivial code cleanup patches
Date: Mon, 25 Mar 2024 18:23:30 +0100 [thread overview]
Message-ID: <2024032552-ardently-colonial-8502@gregkh> (raw)
In-Reply-To: <cover.1710965653.git.ayushtiw0110@gmail.com>
On Thu, Mar 21, 2024 at 02:44:51AM +0530, Ayush Tiwari wrote:
> Address different kinds of checkpatch complains for the rtl8712 module
> to ensure adherence to coding style guidelines.
>
> 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 subject line for this 0/3 email does not give us a hint as to what
these changes are for. Please resend the next version with something
like:
staging: rtl8712: .....
so that we know what to expect.
thanks,
greg k-h
prev parent reply other threads:[~2024-03-25 17:23 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
2024-03-24 20:47 ` [PATCH v4 " Ayush Tiwari
2024-03-25 17:23 ` Greg KH [this message]
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=2024032552-ardently-colonial-8502@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=ayushtiw0110@gmail.com \
--cc=florian.c.schilhabel@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@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 read-only IMAP folder(s) and NNTP newsgroup(s).