From: Felix Schlepper <f3sch.git@outlook.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
wjsota@gmail.com, Felix Schlepper <f3sch.git@outlook.com>
Subject: [PATCH 0/7] Staging: rtl8192e: rtllib_wx.c coding style
Date: Tue, 28 Jun 2022 10:30:49 +0200 [thread overview]
Message-ID: <cover.1656402464.git.f3sch.git@outlook.com> (raw)
This series addresses some issues raised by chechpatch.pl.
There are no logical changes, just addressing coding style.
I 'tested' it by bulding.
Felix Schlepper (7):
Staging: rtl8192e: Added blank lines before/after struct
Staging: rtl8192e: Added spaces around binary operators
Staging: rtl8192e: Avoid multiple assignments
Staging: rtl8192e: Remove unnecessary parentheses
Staging: rtl8192e: Added braces around else
Staging: rtl8192e: Remove unnecessary blank line
Staging: rtl8192e: Added spaces around '+'
drivers/staging/rtl8192e/rtllib_wx.c | 20 ++++++++++++--------
1 file changed, 12 insertions(+), 8 deletions(-)
--
2.36.1
next reply other threads:[~2022-06-28 8:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 8:30 Felix Schlepper [this message]
2022-06-28 8:30 ` [PATCH 1/7] Staging: rtl8192e: Added blank lines before/after struct Felix Schlepper
2022-06-28 17:58 ` Joe Perches
2022-06-29 12:11 ` Felix Schlepper
2022-06-29 18:09 ` Joe Perches
2022-06-28 8:30 ` [PATCH 2/7] Staging: rtl8192e: Added spaces around binary operators Felix Schlepper
2022-06-28 8:30 ` [PATCH 3/7] Staging: rtl8192e: Avoid multiple assignments Felix Schlepper
2022-06-29 16:13 ` Dan Carpenter
2022-06-28 8:30 ` [PATCH 4/7] Staging: rtl8192e: Remove unnecessary parentheses Felix Schlepper
2022-06-28 8:30 ` [PATCH 5/7] Staging: rtl8192e: Added braces around else Felix Schlepper
2022-06-28 8:30 ` [PATCH 6/7] Staging: rtl8192e: Remove unnecessary blank line Felix Schlepper
2022-06-28 8:30 ` [PATCH 7/7] Staging: rtl8192e: Added spaces around '+' Felix Schlepper
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.1656402464.git.f3sch.git@outlook.com \
--to=f3sch.git@outlook.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=wjsota@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 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.