public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Deepak Mishra <linux.dkm@gmail.com>
To: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
	linux.dkm@gmail.com, straube.linux@gmail.com
Subject: [PATCH v5 0/6] staging: rtl8712: cleanup struct _adapter
Date: Sun,  9 Jun 2019 18:01:39 +0530	[thread overview]
Message-ID: <cover.1560081971.git.linux.dkm@gmail.com> (raw)

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  

Following review comments from previous versions are addressed 
1. Separated CamelCase fix for lockRxFF0Filter and wkFilterRxFF0 to
separate patches
2. Separated CamelCase EepromAddressSizefrom removal of unused variable
ImrContent two different patches.
3. Remove redundant code along with removing variable ImrContent from
the structure
4. Instead of fixing CamelCase issue, remove the variables not in use.
5. Fixing of CamelCase of variable blnEnableRxFF0Filter is removed
from this patch set as spinning on a random variable for synchronization
needs to be fixed separately
 
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

 drivers/staging/rtl8712/drv_types.h        | 13 ++++---------
 drivers/staging/rtl8712/os_intfs.c         |  6 +++---
 drivers/staging/rtl8712/rtl871x_eeprom.c   |  6 +++---
 drivers/staging/rtl8712/rtl871x_mp_ioctl.c |  5 -----
 drivers/staging/rtl8712/rtl871x_xmit.c     |  2 +-
 drivers/staging/rtl8712/usb_intf.c         |  4 ++--
 drivers/staging/rtl8712/xmit_linux.c       |  6 +++---
 7 files changed, 16 insertions(+), 26 deletions(-)

-- 
2.19.1


             reply	other threads:[~2019-06-09 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09 12:31 Deepak Mishra [this message]
2019-06-09 12:31 ` [PATCH v5 1/6] staging: rtl8712: Fixed CamelCase for EepromAddressSize Deepak Mishra
2019-06-09 12:31 ` [PATCH v5 2/6] staging: rtl8712: Removed redundant code from function oid_rt_pro_write_register_hdl Deepak Mishra
2019-06-09 12:31 ` [PATCH v5 3/6] staging: rtl8712: Fixed CamelCase cmdThread rename to cmd_thread Deepak Mishra
2019-06-09 12:31 ` [PATCH v5 4/6] staging: rtl8712: removed unused variables from struct _adapter Deepak Mishra
2019-06-09 12:31 ` [PATCH v5 5/6] staging: rtl8712: Renamed CamelCase wkFilterRxFF0 to wk_filter_rx_ff0 Deepak Mishra
2019-06-10 15:58   ` Greg KH
2019-06-09 12:31 ` [PATCH v5 6/6] staging: rtl8712: Renamed CamelCase lockRxFF0Filter to lock_rx_ff0_filter Deepak Mishra

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=cover.1560081971.git.linux.dkm@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