From: Deepak Mishra <linux.dkm@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, Larry.Finger@lwfinger.net,
florian.c.schilhabel@googlemail.com, linux.dkm@gmail.com,
himadri18.07@gmail.com, straube.linux@gmail.com
Subject: [PATCH 0/8] staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
Date: Sun, 2 Jun 2019 00:13:34 +0530 [thread overview]
Message-ID: <cover.1559412149.git.linux.dkm@gmail.com> (raw)
This patchset fixes CamelCase checks in struct _adapter in drv_types.h
and in files where struct _adapter is used by renaming the variables
without camel case.
These check were reported by checkpatch.pl
Deepak Mishra (8):
staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h
drivers/staging/rtl8712/drv_types.h | 18 +++++++++---------
drivers/staging/rtl8712/os_intfs.c | 6 +++---
drivers/staging/rtl8712/rtl871x_cmd.c | 2 +-
drivers/staging/rtl8712/rtl871x_eeprom.c | 6 +++---
drivers/staging/rtl8712/rtl871x_mp_ioctl.c | 2 +-
drivers/staging/rtl8712/rtl871x_pwrctrl.h | 2 +-
drivers/staging/rtl8712/rtl871x_xmit.c | 2 +-
drivers/staging/rtl8712/usb_intf.c | 2 +-
drivers/staging/rtl8712/xmit_linux.c | 6 +++---
9 files changed, 23 insertions(+), 23 deletions(-)
--
2.19.1
next reply other threads:[~2019-06-01 18:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 18:43 Deepak Mishra [this message]
2019-06-01 18:43 ` [PATCH 1/8] staging: rtl8712: Fixed CamelCase in struct _adapter from drv_types.h Deepak Mishra
2019-06-01 18:43 ` [PATCH 2/8] " Deepak Mishra
2019-06-01 18:43 ` [PATCH 3/8] " Deepak Mishra
2019-06-01 18:43 ` [PATCH 4/8] " Deepak Mishra
2019-06-01 18:43 ` [PATCH 5/8] " Deepak Mishra
2019-06-01 18:43 ` [PATCH 6/8] " Deepak Mishra
2019-06-01 18:43 ` [PATCH 7/8] " Deepak Mishra
2019-06-01 18:43 ` [PATCH 8/8] " Deepak Mishra
2019-06-01 19:26 ` Joe Perches
2019-06-02 10:12 ` Deepak Mishra
2019-06-02 6:20 ` [PATCH 0/8] " 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=cover.1559412149.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=himadri18.07@gmail.com \
--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