From: "Frank A. Cancio Bello" <frank@generalsoftwareinc.com>
To: pablo@netfilter.org, Julia.Lawall@lip6.fr
Cc: gregkh@linuxfoundation.org, outreachy-kernel@googlegroups.com
Subject: [PATCH 0/4] staging: rtlwifi: rtl8822be: Fix code styling issues and the hardcode of a func name
Date: Tue, 17 Oct 2017 23:24:55 -0400 [thread overview]
Message-ID: <cover.1508295702.git.frank@generalsoftwareinc.com> (raw)
This patchset address code style issues with braces, parentheses and
comments. Beside it include a fix to a hardcoded function's name.
This is my first patchset ever, so I decided to keep it small to make it easy
to correct or apply if it is OK.
Frank A. Cancio Bello (4):
staging: rtlwifi: rtl8822be: Balance else statement braces
staging: rtlwifi: rtl8822be: Use __func__ instead of hardcoded name
staging: rtlwifi: rtl8822be: Remove useless parentheses
staging: rtlwifi: rtl8822be: Align the * in block comment
drivers/staging/rtlwifi/rtl8822be/fw.c | 7 ++++---
drivers/staging/rtlwifi/rtl8822be/led.c | 2 +-
drivers/staging/rtlwifi/rtl8822be/phy.c | 19 ++++++++++---------
drivers/staging/rtlwifi/rtl8822be/trx.c | 24 ++++++++++++------------
4 files changed, 27 insertions(+), 25 deletions(-)
--
2.7.4
next reply other threads:[~2017-10-18 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 3:24 Frank A. Cancio Bello [this message]
2017-10-18 3:30 ` [PATCH 1/4] staging: rtlwifi: rtl8822be: Balance braces in else statement Frank A. Cancio Bello
2017-10-18 3:33 ` [PATCH 2/4] staging: rtlwifi: rtl8822be: Use __func__ instead of hardcoded name Frank A. Cancio Bello
2017-10-18 3:35 ` [PATCH 3/4] staging: rtlwifi: rtl8822be: Remove useless parentheses Frank A. Cancio Bello
2017-10-18 3:37 ` [PATCH 4/4] staging: rtlwifi: rtl8822be: Align the * in block comment Frank A. Cancio Bello
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.1508295702.git.frank@generalsoftwareinc.com \
--to=frank@generalsoftwareinc.com \
--cc=Julia.Lawall@lip6.fr \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.