From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Tree Davies <tdavies@darkphysics.net>,
gregkh@linuxfoundation.org, anjan@momi.ca, error27@gmail.com
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/12] Staging: rtl8192e: Style Guide Cleanup
Date: Fri, 14 Jul 2023 07:09:56 +0200 [thread overview]
Message-ID: <92728470-692d-b99e-db57-1a2805eaabf0@gmail.com> (raw)
In-Reply-To: <ZK82AIxHctHFc27N@basil>
On 7/13/23 01:23, Tree Davies wrote:
> This patch series fixes checkpatch CamelCase warnings
> in regard to drivers/staging/rtl8192e/rtl819x_BAProc.c
>
> Tree Davies (12):
> Staging: rtl8192e: Rename function ActivateBAEntry
> Staging: rtl8192e: Rename function DeActivateBAEntry
> Staging: rtl8192e: Rename function TxTsDeleteBA
> Staging: rtl8192e: Rename function TsInitAddBA
> Staging: rtl8192e: Rename function TsInitDelBA
> Staging: rtl8192e: Rename function BaSetupTimeOut
> Staging: rtl8192e: Rename function TxBaInactTimeout
> Staging: rtl8192e: Rename function RxBaInactTimeout
> Staging: rtl8192e: Rename variable pBA
> Staging: rtl8192e: Rename variable Time
> Staging: rtl8192e: Rename variable pTxTs
> Staging: rtl8192e: Rename variable TxAdmittedBARecord
>
> drivers/staging/rtl8192e/rtl819x_BAProc.c | 186 +++++++++++-----------
> drivers/staging/rtl8192e/rtl819x_TS.h | 2 +-
> drivers/staging/rtl8192e/rtl819x_TSProc.c | 20 +--
> drivers/staging/rtl8192e/rtllib.h | 12 +-
> drivers/staging/rtl8192e/rtllib_tx.c | 18 +--
> 5 files changed, 119 insertions(+), 119 deletions(-)
>
Hi Tree,
please make the Subject more unique. Otherwise some programs/homepages
for reading this emails are not showing the Emails that belong together
correct. But it is also for us readers good to have different email
subjects.
Please have a look at:
https://lore.kernel.org/linux-staging/
for your patches. Usually a patch series is shown together but yours is
not. May be this has to do with taking to much time between sending the
emails (patches). If you use mutt to send then I recommend to open 13
Terminals and prepare all those windows for sending. Then send them all
quick one after another.
For this homepage it is OK:
https://www.spinics.net/lists/linux-staging/
This does not need to be corrected now. May be to be considered for the
next time.
Bye Philipp
prev parent reply other threads:[~2023-07-14 5:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 23:23 [PATCH 00/12] Staging: rtl8192e: Style Guide Cleanup Tree Davies
2023-07-14 5:09 ` 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=92728470-692d-b99e-db57-1a2805eaabf0@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=anjan@momi.ca \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=tdavies@darkphysics.net \
/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