All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Rookard <garyrookard@fastmail.org>
To: Gary Rookard <garyrookard@fastmail.org>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
	gregkh@linuxfoundation.org, philipp.g.hortmann@gmail.com,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] staging: rtl8192e: rename variable is40MHz
Date: Mon, 08 Jan 2024 20:25:55 -0500	[thread overview]
Message-ID: <871qarcmzt.fsf@fastmail.org> (raw)
In-Reply-To: <62836460ae502097ca8307bcee85a5ae3634e1acc74af843ffc466c28d1a0b95@mu.id>

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


Gary Rookard <garyrookard@fastmail.org> writes:

> Gary Rookard <garyrookard@fastmail.org> writes:
>
>> [[PGP Signed Part:Undecided]]
>>
>> Dan Carpenter <dan.carpenter@linaro.org> writes:
>>
>>> On Sun, Jan 07, 2024 at 10:22:29PM -0500, Gary Rookard wrote:
>>>> Coding style issue, checkpatch avoid CamelCase,
>>>> rename it. is40MHz -> is_40mhz
>>>> 
>>>> Signed-off-by: Gary Rookard <garyrookard@fastmail.org>
>>>> ---
>>>>  drivers/staging/rtl8192e/rtl819x_HTProc.c | 16 ++++++++--------
>>>>  1 file changed, 8 insertions(+), 8 deletions(-)
>>>> 
>>>> diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c b/drivers/staging/rtl8192e/rtl819x_HTProc.c
>>>> index 6d0912f90198..1b1cb9514028 100644
>>>> --- a/drivers/staging/rtl8192e/rtl819x_HTProc.c
>>>> +++ b/drivers/staging/rtl8192e/rtl819x_HTProc.c
>>>> @@ -87,36 +87,36 @@ static u16 ht_mcs_to_data_rate(struct rtllib_device *ieee, u8 mcs_rate)
>>>>  {
>>>>  	struct rt_hi_throughput *ht_info = ieee->ht_info;
>>>>  
>>>> -	u8	is40MHz = (ht_info->cur_bw_40mhz) ? 1 : 0;
>>>> +	u8	is_40mhz = (ht_info->cur_bw_40mhz) ? 1 : 0;
>>>
>>> This should be is_40MHz.  It's metric.  M means Mega.  m means milli.
>>>
>>> regards,
>>> dan carpenter
>> --
>> Okay, stupid me didin't give it to much thought that way,
>> ...wow there's more that way then just mine
>> Good catch!
>> Regards,
>> Gary
--
There's only mine that I can find, I'll fix them up
and resubmit them.

Thanks for your insight.

Regards,
Gary
-- 
Sent with my mu4e on Void GNU/Linux.

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

  parent reply	other threads:[~2024-01-09  1:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08  3:22 [PATCH 0/5] staging: rtl8192e: renamed variable is40MHz and 4 other Gary Rookard
2024-01-08  3:22 ` [PATCH 1/5] staging: rtl8192e: rename variable is40MHz Gary Rookard
2024-01-08  7:58   ` Dan Carpenter
2024-01-08 13:22     ` Gary Rookard
     [not found]       ` <62836460ae502097ca8307bcee85a5ae3634e1acc74af843ffc466c28d1a0b95@mu.id>
2024-01-09  1:25         ` Gary Rookard [this message]
2024-01-09  7:43           ` Dan Carpenter
2024-01-08  3:22 ` [PATCH 2/5] staging: rtl8192e: rename variable isShortGI Gary Rookard
2024-01-08  3:22 ` [PATCH 3/5] staging: rtl8192e: rename variable retValue Gary Rookard
2024-01-08  3:22 ` [PATCH 4/5] staging: rtl8192e: rename variable EWC11NHTCap Gary Rookard
2024-01-08  3:22 ` [PATCH 5/5] staging: rtl8192e: rename variable AdvCoding Gary Rookard
2024-01-08  4:46 ` [PATCH 0/5] staging: rtl8192e: renamed variable is40MHz and 4 other Philipp Hortmann

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=871qarcmzt.fsf@fastmail.org \
    --to=garyrookard@fastmail.org \
    --cc=dan.carpenter@linaro.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 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.