From: Deepak Kumar Mishra <linux.dkm@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Larry.Finger@lwfinger.net,
florian.c.schilhabel@googlemail.com, straube.linux@gmail.com
Subject: Re: [PATCH v4 0/6] staging: rtl8712: cleanup struct _adapter
Date: Sun, 9 Jun 2019 17:16:48 +0530 [thread overview]
Message-ID: <933b8890-986c-8bdb-93ef-90edf248fb43@gmail.com> (raw)
In-Reply-To: <20190609111010.GA28875@kroah.com>
Hi Greg,
On 09/06/19 4:40 PM, Greg KH wrote:
> On Sat, Jun 08, 2019 at 04:26:55PM +0530, Deepak Mishra wrote:
>> In process of cleaning up rtl8712 struct _adapter in drv_types.h I have
>> tried to remove some unused variables and redundant lines of code
>> associated with those variables. I have also fixed some CamelCase
>> reported by checkpatch.pl
>>
>> Deepak Mishra (6):
>> staging: rtl8712: Fixed CamelCase for EepromAddressSize
>> staging: rtl8712: Removed redundant code from function
>> oid_rt_pro_write_register_hdl
>> staging: rtl8712: Fixed CamelCase cmdThread rename to cmd_thread
>> staging: rtl8712: removed unused variables from struct _adapter
>> staging: rtl8712: Renamed CamelCase wkFilterRxFF0 to wk_filter_rx_ff0
>> staging: rtl8712: Renamed CamelCase lockRxFF0Filter to
>> lock_rx_ff0_filter
> If this is a "v4" series, I do not see a list of what has changed from
> the previous versions at all here :(
>
> Please list it somewhere, usually in the individual patches below the
> --- line, or you can put it here in the 00/XX email as well.
>
> v5 please?
In my previous versions I mainly tried to correct the patch submission
based on your suggestion for example
1.keeping every individual task separate.
2. Not only just fix CamelCase but if those variables are unused remove
those.
3. If any variable is assigned but never used then remove those.
So should I put these review comments in my 0/6 file and send you the v5
of the patch set,
or remove version number and send a new patch set again as if it is a
fresh patch set ?
Please suggest.
Best regards
Deepak Mishra
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2019-06-09 11:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 10:56 Deepak Mishra
2019-06-08 10:56 ` [PATCH v4 1/6] staging: rtl8712: Fixed CamelCase for EepromAddressSize Deepak Mishra
2019-06-08 10:56 ` [PATCH v4 2/6] staging: rtl8712: Removed redundant code from function oid_rt_pro_write_register_hdl Deepak Mishra
2019-06-08 10:56 ` [PATCH v4 3/6] staging: rtl8712: Fixed CamelCase cmdThread rename to cmd_thread Deepak Mishra
2019-06-08 10:56 ` [PATCH v4 4/6] staging: rtl8712: removed unused variables from struct _adapter Deepak Mishra
2019-06-08 10:57 ` [PATCH v4 5/6] staging: rtl8712: Renamed CamelCase wkFilterRxFF0 to wk_filter_rx_ff0 Deepak Mishra
2019-06-08 10:57 ` [PATCH v4 6/6] staging: rtl8712: Renamed CamelCase lockRxFF0Filter to lock_rx_ff0_filter Deepak Mishra
2019-06-09 11:10 ` [PATCH v4 0/6] staging: rtl8712: cleanup struct _adapter Greg KH
2019-06-09 11:46 ` Deepak Kumar Mishra [this message]
2019-06-09 12:01 ` 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=933b8890-986c-8bdb-93ef-90edf248fb43@gmail.com \
--to=linux.dkm@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=straube.linux@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome