From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Yogesh Hegde <yogi.kernel@gmail.com>,
gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: linux-kernel-mentees@lists.linuxfoundation.org,
skhan@linuxfoundation.org, ivan.orlov0322@gmail.com
Subject: Re: [PATCH 0/4] Trivial code cleanup patches
Date: Thu, 6 Jul 2023 17:30:27 +0200 [thread overview]
Message-ID: <8e53be9b-8b47-597d-1538-95733eb16cac@gmail.com> (raw)
In-Reply-To: <cover.1688299890.git.yogi.kernel@gmail.com>
On 7/2/23 14:14, Yogesh Hegde wrote:
> Rename variables in function _rtl92e_dm_check_rate_adaptive
> to avoid checkpatch complains.
>
> The patches are required to be applied in sequence.
>
> Yogesh Hegde (4):
> staging: rtl8192e: Rename variable currentRATR
> staging: rtl8192e: Rename variable targetRATR
> staging: rtl8192e: Rename variable LowRSSIThreshForRA
> staging: rtl8192e: Rename variable HighRSSIThreshForRA
>
> drivers/staging/rtl8192e/rtl8192e/rtl_dm.c | 38 +++++++++++-----------
> 1 file changed, 19 insertions(+), 19 deletions(-)
>
Please use the "staging: rtl8192e:" also for the cover letter in the
subject for the next patch series you are sending.
Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>
next prev parent reply other threads:[~2023-07-06 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 12:14 [PATCH 0/4] Trivial code cleanup patches Yogesh Hegde
2023-07-02 12:15 ` [PATCH 1/4] staging: rtl8192e: Rename variable currentRATR Yogesh Hegde
2023-07-02 12:15 ` [PATCH 2/4] staging: rtl8192e: Rename variable targetRATR Yogesh Hegde
2023-07-02 12:16 ` [PATCH 3/4] staging: rtl8192e: Rename variable LowRSSIThreshForRA Yogesh Hegde
2023-07-02 12:16 ` [PATCH 4/4] staging: rtl8192e: Rename variable HighRSSIThreshForRA Yogesh Hegde
2023-07-06 15:30 ` Philipp Hortmann [this message]
2023-07-08 6:42 ` [PATCH 0/4] Trivial code cleanup patches Yogesh Hegde
-- strict thread matches above, loose matches on Subject: below --
2023-05-28 14:51 Yogesh Hegde
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=8e53be9b-8b47-597d-1538-95733eb16cac@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ivan.orlov0322@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
--cc=yogi.kernel@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