mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	samirweng1979 <samirweng1979@163.com>
Cc: <linux-wireless@vger.kernel.org>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	wengjianfeng <wengjianfeng@yulong.com>, <davem@davemloft.net>,
	<kuba@kernel.org>
Subject: Re: [PATCH] wireless: fix typo issue
Date: Wed, 3 Feb 2021 15:51:36 +0800	[thread overview]
Message-ID: <74d4dfc5-51ae-5f53-6210-2cc14da55dcb@huawei.com> (raw)
In-Reply-To: <9200710b2d9dafea4bfae4bb449a55fb44245d04.camel@sipsolutions.net>

On 2021/2/3 15:33, Johannes Berg wrote:
> On Wed, 2021-02-03 at 15:00 +0800, samirweng1979 wrote:
>> From: wengjianfeng <wengjianfeng@yulong.com>
>>
>> change 'iff' to 'if'.
>>
>> Signed-off-by: wengjianfeng <wengjianfeng@yulong.com>
>> ---
>>  net/wireless/chan.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/net/wireless/chan.c b/net/wireless/chan.c
>> index 285b807..2f17edf 100644
>> --- a/net/wireless/chan.c
>> +++ b/net/wireless/chan.c
>> @@ -1084,7 +1084,7 @@ bool cfg80211_chandef_usable(struct wiphy *wiphy,
>>   * associated to an AP on the same channel or on the same UNII band
>>   * (assuming that the AP is an authorized master).
>>   * In addition allow operation on a channel on which indoor operation is
>> - * allowed, iff we are currently operating in an indoor environment.
>> + * allowed, if we are currently operating in an indoor environment.
>>   */
> 
> I suspect that was intentional, as a common abbreviation for "if and
> only if".

Yep. iff --> if and only if from:
https://mathvault.ca/math-glossary/#iff

> 
> johannes
> 
> .
> 


  reply	other threads:[~2021-02-03  7:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210203070025.17628-1-samirweng1979@163.com>
2021-02-03  7:33 ` Johannes Berg
2021-02-03  7:51   ` Miaohe Lin [this message]
2021-02-03  7:56     ` wengjianfeng

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=74d4dfc5-51ae-5f53-6210-2cc14da55dcb@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=davem@davemloft.net \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=samirweng1979@163.com \
    --cc=wengjianfeng@yulong.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®