From: Pavel Skripkin <paskripkin@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] Staging: r8188eu: core: rtw_xmit: Fixed a few coding style issues
Date: Sun, 19 Jun 2022 16:27:21 +0300 [thread overview]
Message-ID: <91c9a0de-76f8-37fb-31b4-4401a6e35d48@gmail.com> (raw)
In-Reply-To: <20220618204454.16071-1-marcus.yu.56@gmail.com>
Hi Chang,
On 6/18/22 23:44, Chang Yu wrote:
> Fixed a few coding style issues and spelling errors in the comments.
>
> Signed-off-by: Chang Yu <marcus.yu.56@gmail.com>
> ---
You are doing a lot of different changes in one patch. Please, separate
each clean up into its own patch
Thanks,
--Pavel Skripkin
next prev parent reply other threads:[~2022-06-19 13:27 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 [this message]
2022-06-19 19:42 ` [PATCH v2 0/5] Fixed some coding style issues and spelling Chang Yu
2022-06-19 19:42 ` [PATCH v2 1/5] Staging: r8188eu: core: rtw_xmit: Fixed some whitespace coding style issues 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=91c9a0de-76f8-37fb-31b4-4401a6e35d48@gmail.com \
--to=paskripkin@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