From: Dan Carpenter <dan.carpenter@linaro.org>
To: Gary Rookard <garyrookard@fastmail.org>
Cc: 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: Tue, 9 Jan 2024 10:43:39 +0300 [thread overview]
Message-ID: <2273e640-0e30-468f-804f-c5699e5225dc@moroto.mountain> (raw)
In-Reply-To: <871qarcmzt.fsf@fastmail.org>
On Mon, Jan 08, 2024 at 08:25:55PM -0500, Gary Rookard wrote:
> >>> 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 this and for looking at the surrounding code as well.
regards,
dan carpenter
next prev parent reply other threads:[~2024-01-09 7:43 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
2024-01-09 7:43 ` Dan Carpenter [this message]
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=2273e640-0e30-468f-804f-c5699e5225dc@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=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
all inboxes | Powered by JetHome®