From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Chang Yu <marcus.yu.56@gmail.com>, Larry.Finger@lwfinger.net
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] staging: r8188eu: Fixed some coding style issues
Date: Wed, 22 Jun 2022 07:16:27 +0200 [thread overview]
Message-ID: <e16221e9-c739-ea68-b5a7-7b48b7766113@gmail.com> (raw)
In-Reply-To: <cover.1655872968.git.marcus.yu.56@gmail.com>
On 6/22/22 06:52, Chang Yu wrote:
> Fixed a few coding style issues as per checkpatch.pl and kernel coding
> style guidelines.
>
> Chang Yu (5):
> staging: r8188eu: Fixed a function declaration coding style issue
> staging: r8188eu: Fixed two brace coding style issues
> staging: r8188eu: Fixed two whitespace coding style issues
> staging: r8188eu: Fixed comment style
> staging: r8188eu: Fixed some blank line coding style issues
>
> drivers/staging/r8188eu/core/rtw_recv.c | 38 +++++++++++++++----------
> 1 file changed, 23 insertions(+), 15 deletions(-)
>
Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com> # Edimax N150
Adapter
prev parent reply other threads:[~2022-06-22 5:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 4:52 [PATCH 0/5] staging: r8188eu: Fixed some coding style issues Chang Yu
2022-06-22 4:52 ` [PATCH 1/5] staging: r8188eu: Fixed a function declaration coding style issue Chang Yu
2022-06-22 9:32 ` Greg KH
2022-06-22 4:52 ` [PATCH 2/5] staging: r8188eu: Fixed two brace coding style issues Chang Yu
2022-06-22 4:52 ` [PATCH 3/5] staging: r8188eu: Fixed two whitespace " Chang Yu
2022-06-22 4:52 ` [PATCH 4/5] staging: r8188eu: Fixed comment style Chang Yu
2022-06-22 4:52 ` [PATCH 5/5] staging: r8188eu: Fixed some blank line coding style issues Chang Yu
2022-06-22 5:16 ` Philipp Hortmann [this message]
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=e16221e9-c739-ea68-b5a7-7b48b7766113@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=marcus.yu.56@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