From: Aditya Jain <aditya.jainadityajain.jain@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org,
Aditya Jain <aditya.jainadityajain.jain@gmail.com>,
linux-kernel@vger.kernel.org, hdegoede@redhat.com,
joe@perches.com, Larry.Finger@lwfinger.net
Subject: [PATCH v4 0/3] Fix coding style issues in staging
Date: Thu, 30 Jul 2020 00:51:33 +0530 [thread overview]
Message-ID: <20200729192136.23828-1-aditya.jainadityajain.jain@gmail.com> (raw)
In-Reply-To: <CAJAoDUjVBon2iiztdER82mHgJtVS6s5XYSajbCTne0KWAzoLvg@mail.gmail.com>
Hey everyone,
Following the comments received I've updated the patch.
The patch cleans up coding style issues in the file
drivers/staging/rtl8723bs/include/hal_phy_cfg.h
Changelog:
v1:
Fixed ERROR: "foo * bar" should be "foo *bar" reported by
checkpatch.pl
v1 -> v2:
Cleaned up multiline function declarations as suggested
by Greg and adjusted spacing in macro definitions to align them.
v2 -> v3:
Broke the single patch in v2 into multiple patches with each
patch doing one single task.
v3 -> v4:
1. Corrected the patch subject following Larry's suggestion.
2. Merged the second and third patches into one following Greg's
comment.
3. Removed comments from the PHY_SetBWMode8723B function declaration.
Aditya Jain (3):
staging: rtl8723bs: Fix coding style errors
staging: rtl8723bs: Clean up function declations
staging: rtl8723bs: Align macro definitions
.../staging/rtl8723bs/include/hal_phy_cfg.h | 116 +++++-------------
1 file changed, 32 insertions(+), 84 deletions(-)
--
2.25.1
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2020-07-29 19:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 8:02 [PATCH] staging: rtl8723bs: include: Fix coding style errors Aditya Jain
2020-07-26 8:26 ` Greg KH
2020-07-26 8:40 ` Aditya Jain
2020-07-26 10:53 ` [PATCH v2] staging: rtl8723bs: include: Fix coding style issues Aditya Jain
2020-07-26 10:59 ` Greg KH
2020-07-26 14:18 ` Fix code style issues in staging Aditya Jain
2020-07-26 14:20 ` [PATCH v3 1/4] staging: rtl8723bs: include: Fix coding style errors Aditya Jain
2020-07-26 14:20 ` [PATCH v3 2/4] staging: rtl8723bs: include: Clean up function declations Aditya Jain
2020-07-26 14:20 ` [PATCH v3 3/4] staging: rtl8723bs: include: Further clean up function declarations Aditya Jain
2020-07-26 15:02 ` Greg KH
2020-07-26 17:15 ` Joe Perches
2020-07-26 18:15 ` Aditya Jain
2020-07-28 20:03 ` Aditya Jain
2020-07-26 14:20 ` [PATCH v3 4/4] staging: rtl8723bs: include: Align macro definitions Aditya Jain
2020-07-26 18:03 ` [PATCH] staging: rtl8723bs: include: Fix coding style errors Larry Finger
2020-07-26 18:29 ` Aditya Jain
2020-07-29 19:21 ` Aditya Jain [this message]
2020-07-29 19:21 ` [PATCH v4 1/3] staging: rtl8723bs: " Aditya Jain
2020-07-29 19:21 ` [PATCH v4 2/3] staging: rtl8723bs: Clean up function declations Aditya Jain
2020-07-29 19:21 ` [PATCH v4 3/3] staging: rtl8723bs: Align macro definitions Aditya Jain
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=20200729192136.23828-1-aditya.jainadityajain.jain@gmail.com \
--to=aditya.jainadityajain.jain@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).