From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Gary Rookard <garyrookard@fastmail.org>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] staging: rtl8192e: patch series renames (5) different variables
Date: Sat, 9 Dec 2023 18:16:55 +0100 [thread overview]
Message-ID: <fec3284b-ee1d-4c53-8f01-76ab209584b8@gmail.com> (raw)
In-Reply-To: <87y1e4dy2g.fsf@fastmail.org>
On 12/8/23 22:56, Gary Rookard wrote:
>
> Philipp Hortmann <philipp.g.hortmann@gmail.com> writes:
>
>> On 12/8/23 02:55, Gary Rookard wrote:
>>> Hi,
>>> This patch series renames 5 different variables with the checkpatch
>>> coding style issue, Avoid CamelCase.
>>> Patch 1/5) renamed variable bCurShortGI40MHz
>>> Patch 2/5) renamed variable bcurShortGI20MHz
>>> Patch 3/5) renamed variable CCKOFDMRate
>>> Patch 4/5) renamed variable HTIOTActIsCCDFsync
>>> Patch 5/5) renamed variable IOTPeer
>>> Signed-off-by: Gary Rookard <garyrookard@fastmail.org>
>>> Gary Rookard (5):
>>> staging: rtl8192e: renamed variable bCurShortGI40MHz
>>> staging: rtl8192e: renamed variable bCurShortGI20MHz
>>> staging: rtl8192e: renamed variable CCKOFDMRate
>>> staging: rtl8192e: renamed variable HTIOTActIsCCDFsync
>>> staging: rtl8192e: renamed variable IOTPeer
>>> .../staging/rtl8192e/rtl8192e/r8192E_dev.c | 4 +-
>>> drivers/staging/rtl8192e/rtl8192e/rtl_dm.c | 22 +++----
>>> drivers/staging/rtl8192e/rtl819x_HT.h | 6 +-
>>> drivers/staging/rtl8192e/rtl819x_HTProc.c | 58 +++++++++----------
>>> drivers/staging/rtl8192e/rtllib_tx.c | 4 +-
>>> 5 files changed, 47 insertions(+), 47 deletions(-)
>>>
>>
>>
>> Please use present-tense as outlined here:
>> https://kernelnewbies.org/PatchPhilosophy
>> So rename instead of renamed
>>
>> Please use a more unique Subject for your coverletter.
>> It often cannot cover everything. But more unique is better.
>>
>>
>>
>> Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>
>
> Okay, "rename" it be, instead of me thinking in the past simple tense,
> of "renamed".
>
> As for the coverletter(s)...repetition a big problem.
>
> There's not much in the way of uniqueness that can be added...regretfully
> Tagging the Subject line with a numeric value is possible and
> should deviate the coverletter(s) enough so they don't "appear the same".
> e.g. staging: rtl8192e: this patch series (1) blah blah blah...
> e.g. staging: rtl8192e: this patch series (2) blah blah blah...
> e.g. staging: rtl8192e: this patch series (3) " " "
>
> Regards,
> Gary
>
Hi Gary
Here is a proposal:
[PATCH 0/5] staging: rtl8192e: Rename variable bCurShortGI40MHz and further
That will give a pretty good recognizable name.
Thanks for your support.
Bye Philipp
next prev parent reply other threads:[~2023-12-09 17:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 1:55 [PATCH 0/5] staging: rtl8192e: patch series renames (5) different variables Gary Rookard
2023-12-08 1:55 ` [PATCH 1/5] staging: rtl8192e: renamed variable bCurShortGI40MHz Gary Rookard
2023-12-08 1:55 ` [PATCH 2/5] staging: rtl8192e: renamed variable bCurShortGI20MHz Gary Rookard
2023-12-08 1:55 ` [PATCH 3/5] staging: rtl8192e: renamed variable CCKOFDMRate Gary Rookard
2023-12-08 1:55 ` [PATCH 4/5] staging: rtl8192e: renamed variable HTIOTActIsCCDFsync Gary Rookard
2023-12-08 17:49 ` [PATCH 0/5] staging: rtl8192e: patch series renames (5) different variables Philipp Hortmann
2023-12-08 21:56 ` Gary Rookard
2023-12-09 17:16 ` Philipp Hortmann [this message]
2023-12-09 0:41 ` Gary Rookard
-- strict thread matches above, loose matches on Subject: below --
2023-12-05 23:16 Gary Rookard
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=fec3284b-ee1d-4c53-8f01-76ab209584b8@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=garyrookard@fastmail.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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