From: Gary Rookard <garyrookard@fastmail.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: philipp.g.hortmann@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] [Series 4] staging: rtl8192e: rename variable pHT and (3) other
Date: Sat, 16 Dec 2023 08:09:50 -0500 [thread overview]
Message-ID: <87fs02l26z.fsf@fastmail.org> (raw)
In-Reply-To: <2023121627-armless-value-6fd7@gregkh>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
Greg KH <gregkh@linuxfoundation.org> writes:
> On Fri, Dec 15, 2023 at 08:01:01PM -0500, Gary Rookard wrote:
>> Hi,
>>
>> This patch series renames (4) different variables with
>> the checkpatch coding style issue, Avoid CamelCase.
>>
>> (resubmittals)
>
> I see two different copies of this patch set, please send only one as
> now I don't know which one is "real".
>
> Please fix up and send a v3, I've dropped both from my queue.
>
> thanks,
>
> greg k-h
--
Sorry for that, I've resent a v3 however 2 got stuck
together resulting in an extra cover letter...
Regards,
Gary
--
Sent with my mu4e on Gentoo GNU/linux.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
next prev parent reply other threads:[~2023-12-16 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 1:01 [PATCH v2 0/4] [Series 4] staging: rtl8192e: rename variable pHT and (3) other Gary Rookard
2023-12-16 1:01 ` [PATCH v2 1/4] staging: rtl8192e: rename variable pHT Gary Rookard
2023-12-16 1:01 ` [PATCH v2 2/4] staging: rtl8192e: rename variable pCapELE Gary Rookard
2023-12-16 1:01 ` [PATCH v2 3/4] staging: rtl8192e: rename variable HTGetHighestMCSRate Gary Rookard
2023-12-16 1:01 ` [PATCH v2 4/4] staging: rtl8192e: renamed variable HTFilterMCSRate Gary Rookard
2023-12-16 7:27 ` [PATCH v2 0/4] [Series 4] staging: rtl8192e: rename variable pHT and (3) other Greg KH
2023-12-16 13:09 ` Gary Rookard [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-15 23:12 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=87fs02l26z.fsf@fastmail.org \
--to=garyrookard@fastmail.org \
--cc=gregkh@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox