From: Chang Yu <marcus.yu.56@gmail.com>
To: Larry.Finger@lwfinger.net, paskripkin@gmail.com
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Chang Yu <marcus.yu.56@gmail.com>
Subject: [PATCH v2 0/5] Fixed some coding style issues and spelling
Date: Sun, 19 Jun 2022 12:42:26 -0700 [thread overview]
Message-ID: <cover.1655666628.git.marcus.yu.56@gmail.com> (raw)
In-Reply-To: <20220618204454.16071-1-marcus.yu.56@gmail.com>
Fixed a few coding style issues and some spelling errors in the
comments.
Changes in v2:
Separated the original big patch into 5 smaller patches so that each
clean up is in its own patch.
Chang Yu (5):
Staging: r8188eu: core: rtw_xmit: Fixed some whitespace coding style
issues
Staging: r8188eu: core: rtw_xmit: Fixed two indentation coding style
issues.
Staging: r8188eu: core: rtw_xmit: Fixed some spelling errors in the
comments
Staging: r8188eu: core: rtw_xmit: Fixed a brace coding style issue
Staging: r8188eu: core: rtw_xmit: Fixed a coding style issue
drivers/staging/r8188eu/core/rtw_xmit.c | 28 ++++++++++---------------
1 file changed, 11 insertions(+), 17 deletions(-)
--
2.36.1
next prev parent reply other threads:[~2022-06-19 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 20:44 [PATCH] Staging: r8188eu: core: rtw_xmit: Fixed a few coding style issues Chang Yu
2022-06-19 13:27 ` Pavel Skripkin
2022-06-19 19:42 ` Chang Yu [this message]
2022-06-19 19:42 ` [PATCH v2 1/5] Staging: r8188eu: core: rtw_xmit: Fixed some whitespace " Chang Yu
2022-06-19 19:42 ` [PATCH v2 2/5] Staging: r8188eu: core: rtw_xmit: Fixed two indentation " Chang Yu
2022-06-19 19:42 ` [PATCH v2 3/5] Staging: r8188eu: core: rtw_xmit: Fixed some spelling errors in the comments Chang Yu
2022-06-19 19:42 ` [PATCH v2 4/5] Staging: r8188eu: core: rtw_xmit: Fixed a brace coding style issue Chang Yu
2022-06-19 19:42 ` [PATCH v2 5/5] Staging: r8188eu: core: rtw_xmit: Fixed a " Chang Yu
2022-06-20 20:04 ` [PATCH v2 0/5] Fixed some coding style issues and spelling Philipp Hortmann
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.1655666628.git.marcus.yu.56@gmail.com \
--to=marcus.yu.56@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=paskripkin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox