From: Luis de Bethencourt <luisbg@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Larry Finger <Larry.Finger@lwfinger.net>,
Hans de Goede <hdegoede@redhat.com>,
Bastien Nocera <hadess@hadess.net>, Arnd Bergmann <arnd@arndb.de>,
Joe Perches <joe@perches.com>,
Luis de Bethencourt <luisbg@kernel.org>
Subject: [PATCH 0/3] staging: rtl8723bs: Fix multiple trailing semicolons
Date: Wed, 10 Jan 2018 13:50:35 +0000 [thread overview]
Message-ID: <20180110135038.32293-1-luisbg@kernel.org> (raw)
Hi,
This is a follow-up of yesterday's water-testing patch [0]. Just 3 more
similar cases of trailing semicolons.
Sending them separately to atomize the changes, but happy to merge them all
into one. It is easier to first try separate and later merge if people want me
to.
In patch 3/3, not sure why this file has so many lines of commented out code.
Maybe I should remove the commented out code instead. pcur_network is clearly
not being used. What do you all think?
Over the weekend I will start running a mainline kernel on my CHIP, and looking
at this driver in more depth. Fun!
Thanks,
Luis
[0] Sorry I don't have a link, LKML is down
Luis de Bethencourt (3):
staging: rtl8723bs: Fix trailing semicolon
staging: rtl8723bs: Fix trailing semicolon
staging: rtl8723bs: Fix trailing semicolon in comment
drivers/staging/rtl8723bs/core/rtw_mlme.c | 2 +-
drivers/staging/rtl8723bs/hal/HalPhyRf_8723B.c | 2 +-
drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--
2.15.1
next reply other threads:[~2018-01-10 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 13:50 Luis de Bethencourt [this message]
2018-01-10 13:50 ` [PATCH 1/3] staging: rtl8723bs: Fix trailing semicolon Luis de Bethencourt
2018-01-10 13:50 ` [PATCH 2/3] " Luis de Bethencourt
2018-01-10 13:50 ` [PATCH 3/3] staging: rtl8723bs: Fix trailing semicolon in comment Luis de Bethencourt
2018-01-10 14:15 ` Dan Carpenter
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=20180110135038.32293-1-luisbg@kernel.org \
--to=luisbg@kernel.org \
--cc=Larry.Finger@lwfinger.net \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hadess@hadess.net \
--cc=hdegoede@redhat.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
/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