From: Johannes Berg <johannes@sipsolutions.net>
To: samirweng1979 <samirweng1979@163.com>,
davem@davemloft.net, kuba@kernel.org
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
wengjianfeng <wengjianfeng@yulong.com>
Subject: Re: [PATCH] wireless: fix typo issue
Date: Wed, 03 Feb 2021 08:33:23 +0100 [thread overview]
Message-ID: <9200710b2d9dafea4bfae4bb449a55fb44245d04.camel@sipsolutions.net> (raw)
In-Reply-To: <20210203070025.17628-1-samirweng1979@163.com>
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".
johannes
next parent reply other threads:[~2021-02-03 7:34 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 [this message]
2021-02-03 7:51 ` Miaohe Lin
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=9200710b2d9dafea4bfae4bb449a55fb44245d04.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.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
Powered by JetHome