From: Greg KH <gregkh@linuxfoundation.org>
To: Gary Rookard <garyrookard@fastmail.org>
Cc: philipp.g.hortmann@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] [Series 3] rename variable HTGetHighestMCSRate and (4) other
Date: Fri, 15 Dec 2023 13:38:33 +0100 [thread overview]
Message-ID: <2023121508-onboard-acutely-3640@gregkh> (raw)
In-Reply-To: <20231213175459.5425-1-garyrookard@fastmail.org>
On Wed, Dec 13, 2023 at 12:54:54PM -0500, Gary Rookard wrote:
> Hi,
>
> This patch series renames (5) different variables with
> the checkpatch coding style issue Avoid CamelCase.
>
> Patch 1/5) rename variable HTGetHighestMCSRate
> Patch 2/5) rename variable HTFilterMCSRate
> Patch 3/5) rename variable HTSetConnectBwMode
> Patch 4/5) rename variable HTOnAssocRsp
> Patch 5/5) rename variable HTInitializeHTInfo
>
> Signed-off-by: Gary Rookard <garyrookard@fastmail.org>
As was pointed out, not all of these patches will apply against my tree
(same for your previous series.) Please rebase all of these and
resubmit the remaining ones.
thanks,
greg k-h
prev parent reply other threads:[~2023-12-15 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 17:54 [PATCH 0/5] [Series 3] rename variable HTGetHighestMCSRate and (4) other Gary Rookard
2023-12-13 17:54 ` [PATCH 1/5] staging: rtl8192e: rename variable HTGetHighestMCSRate Gary Rookard
2023-12-13 19:22 ` Philipp Hortmann
2023-12-13 17:54 ` [PATCH 2/5] staging: rtl8192e: rename variable HTFilterMCSRate Gary Rookard
2023-12-13 17:54 ` [PATCH 3/5] staging: rtl8192e: rename variable HTSetConnectBwMode Gary Rookard
2023-12-13 17:54 ` [PATCH 4/5] staging: rtl8192e: rename variable HTOnAssocRsp Gary Rookard
2023-12-13 17:54 ` [PATCH 5/5] staging: rtl8192e: rename variable HTInitializeHTInfo Gary Rookard
2023-12-15 12:38 ` Greg KH [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=2023121508-onboard-acutely-3640@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=garyrookard@fastmail.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.