The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Deepak Mishra <linux.dkm@gmail.com>
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 13:10:10 +0200	[thread overview]
Message-ID: <20190609111010.GA28875@kroah.com> (raw)
In-Reply-To: <cover.1559990697.git.linux.dkm@gmail.com>

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?

thanks,

greg k-h

  parent reply	other threads:[~2019-06-09 11:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-08 10:56 [PATCH v4 0/6] staging: rtl8712: cleanup struct _adapter 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 ` Greg KH [this message]
2019-06-09 11:46   ` [PATCH v4 0/6] staging: rtl8712: cleanup struct _adapter Deepak Kumar Mishra
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=20190609111010.GA28875@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=florian.c.schilhabel@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.dkm@gmail.com \
    --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