public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gary Rookard <garyrookard@fastmail.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: philipp.g.hortmann@gmail.com, linux-staging@list.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] staging: rtl8192e: rename variable HTInitializeBssDesc and (4) other
Date: Thu, 21 Dec 2023 08:06:13 -0500	[thread overview]
Message-ID: <875y0rog7j.fsf@fastmail.org> (raw)
In-Reply-To: <2023122137-account-vitality-9a72@gregkh>

[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]


Greg KH <gregkh@linuxfoundation.org> writes:

> On Wed, Dec 20, 2023 at 10:09:59PM -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 HTInitializeBssDesc
>> Patch 2/5) rename variable HTResetSelfAndSavePeerSetting
>> Patch 3/5) rename variable HTCCheck
>> Patch 4/5) rename variable HTSetConnectBwModeCallback
>> Patch 5/5) rename variable ePeerHTSpecVer
>> 
>> Signed-off-by: Gary Rookard <garyrookard@fastmail.org>
>> 
>> Gary Rookard (5):
>>   staging: rtl8192e: rename variable HTInitializeBssDesc
>>   staging: rtl8192e: rename variable HTResetSelfAndSavePeerSetting
>>   staging: rtl8192e: rename variable HTCCheck
>>   staging: rtl8192e: rename variable HTSetConnectBwModeCallback
>>   staging: rtl8192e: rename variable ePeerHTSpecVer
>> 
>>  drivers/staging/rtl8192e/rtl819x_HT.h     |  2 +-
>>  drivers/staging/rtl8192e/rtl819x_HTProc.c | 16 ++++++++--------
>>  drivers/staging/rtl8192e/rtllib.h         |  6 +++---
>>  drivers/staging/rtl8192e/rtllib_rx.c      |  6 +++---
>>  drivers/staging/rtl8192e/rtllib_softmac.c |  6 +++---
>>  5 files changed, 18 insertions(+), 18 deletions(-)
>
> I see 2 different patch series here sent to the list, both seeming to do
> the same thing?
>
> confused,
>
> greg k-h

Sorry that was caused by an address typo
so it got resent to linux-staging..
new setup on different distro
Regards,
Gary
-- 
Sent with my mu4e on Void Linux.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]

  reply	other threads:[~2023-12-21 13:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21  3:09 [PATCH 0/5] staging: rtl8192e: rename variable HTInitializeBssDesc and (4) other Gary Rookard
2023-12-21  3:10 ` [PATCH 1/5] staging: rtl8192e: rename variable HTInitializeBssDesc Gary Rookard
2023-12-21  3:10 ` [PATCH 2/5] staging: rtl8192e: rename variable HTResetSelfAndSavePeerSetting Gary Rookard
2023-12-21  3:10 ` [PATCH 3/5] staging: rtl8192e: rename variable HTCCheck Gary Rookard
2023-12-21  3:10 ` [PATCH 4/5] staging: rtl8192e: rename variable HTSetConnectBwModeCallback Gary Rookard
2023-12-21  3:10 ` [PATCH 5/5] staging: rtl8192e: rename variable ePeerHTSpecVer Gary Rookard
2023-12-21 12:52 ` [PATCH 0/5] staging: rtl8192e: rename variable HTInitializeBssDesc and (4) other Greg KH
2023-12-21 13:06   ` Gary Rookard [this message]
2023-12-21 13:15     ` Greg KH
2023-12-21 13:19       ` 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=875y0rog7j.fsf@fastmail.org \
    --to=garyrookard@fastmail.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@list.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