From: Tom Rix <trix@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ieee80211: cleanup double word in comment
Date: Tue, 25 Jan 2022 12:03:50 -0800 [thread overview]
Message-ID: <65cbae9c-20dc-6fab-a462-b74468b9303e@redhat.com> (raw)
In-Reply-To: <10efb4246ce9c76403ac54fa06e8ea3d0d87785e.camel@sipsolutions.net>
On 1/25/22 10:19 AM, Johannes Berg wrote:
> On Tue, 2022-01-25 at 10:07 -0800, trix@redhat.com wrote:
>> From: Tom Rix <trix@redhat.com>
>>
>> Remove the second 'that'.
>>
>> Signed-off-by: Tom Rix <trix@redhat.com>
>> ---
>> include/linux/ieee80211.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/include/linux/ieee80211.h b/include/linux/ieee80211.h
>> index 559b6c6449384..5475383936f8b 100644
>> --- a/include/linux/ieee80211.h
>> +++ b/include/linux/ieee80211.h
>> @@ -467,7 +467,7 @@ static inline bool ieee80211_is_data_qos(__le16 fc)
>> static inline bool ieee80211_is_data_present(__le16 fc)
>> {
>> /*
>> - * mask with 0x40 and test that that bit is clear to only return true
>> + * mask with 0x40 and test that bit is clear to only return true
>> * for the data-containing substypes.
>>
> I don't think it's just a duplicate?
>
> ... and (test that) (that bit is clear to ...)
>
> no?
ok, reads ok.
Sorry for the noise.
T
>
> johannes
>
next prev parent reply other threads:[~2022-01-25 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 18:07 trix
2022-01-25 18:19 ` Johannes Berg
2022-01-25 20:03 ` Tom Rix [this message]
2022-01-25 18:30 ` Joe Perches
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=65cbae9c-20dc-6fab-a462-b74468b9303e@redhat.com \
--to=trix@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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®