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 v2 0/6] Staging: rtl8192e: rtllib_wx codingstyle/refactor
Date: Thu, 30 Jun 2022 13:30:13 +0200 [thread overview]
Message-ID: <cover.1656587827.git.f3sch.git@outlook.com> (raw)
This series addresses some issues raised by chechpatch.pl
and some minor refactoring of rtllib_modes[].
v2:
- split multi assignment in two separate steps.
This avoids having 'fixed'='disabled', which
is silly.
- Since there is no formatting of the rtllib_modes[],
one can safely refactor this code into a array of
strings. This allows using functions like strcpy/strlen,
which is less error prone than using a
rtllib_modes.mode_size.
Felix Schlepper (6):
Staging: rtl8192e: Refactored rtllib_modes
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 | 37 +++++++++++-----------------
1 file changed, 14 insertions(+), 23 deletions(-)
--
2.36.1
next reply other threads:[~2022-06-30 11:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 11:30 Felix Schlepper [this message]
2022-06-30 11:30 ` [PATCH v2 1/6] Staging: rtl8192e: Refactored rtllib_modes Felix Schlepper
2022-07-01 7:43 ` Greg KH
2022-06-30 11:30 ` [PATCH v2 2/6] Staging: rtl8192e: Avoid multiple assignments Felix Schlepper
2022-06-30 11:30 ` [PATCH v2 3/6] Staging: rtl8192e: Remove unnecessary parentheses Felix Schlepper
2022-06-30 11:30 ` [PATCH v2 4/6] Staging: rtl8192e: Added braces around else Felix Schlepper
2022-06-30 11:30 ` [PATCH v2 5/6] Staging: rtl8192e: Remove unnecessary blank line Felix Schlepper
2022-06-30 11:30 ` [PATCH v2 6/6] 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.1656587827.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.