From: Yibo Zhao <yiboz@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Zhi Chen <zhichen@codeaurora.org>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH v2] mac80211: remove warning message
Date: Tue, 14 May 2019 17:10:29 +0800 [thread overview]
Message-ID: <ccb48284f0d96e72f4c041e12c943f0a@codeaurora.org> (raw)
In-Reply-To: <7c92f5cf51eaec1d5449698d90f5b6c5ca6c2bea.camel@sipsolutions.net>
On 2019-05-14 17:05, Johannes Berg wrote:
> On Tue, 2019-05-14 at 17:01 +0800, Yibo Zhao wrote:
>> In multiple SSID cases, it takes time to prepare every AP interface
>> to be ready in initializing phase. If a sta already knows everything
>> it
>> needs to join one of the APs and sends authentication to the AP which
>> is not fully prepared at this point of time, AP's channel context
>> could be NULL. As a result, warning message occurs.
>>
> Err, what was the point in sending v2 without any changes?
>
> johannes
Hi Johannes,
I was planning to use WARN_ON_ONCE() in the first place to replace
WARN_ON() then after some discussion, we think removing it could be
better. So the first patch was based on my first version which is sent
incorrectly. Please check again.
Sorry for the confusing.
--
Yibo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Yibo Zhao <yiboz@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
Zhi Chen <zhichen@codeaurora.org>
Subject: Re: [PATCH v2] mac80211: remove warning message
Date: Tue, 14 May 2019 17:10:29 +0800 [thread overview]
Message-ID: <ccb48284f0d96e72f4c041e12c943f0a@codeaurora.org> (raw)
In-Reply-To: <7c92f5cf51eaec1d5449698d90f5b6c5ca6c2bea.camel@sipsolutions.net>
On 2019-05-14 17:05, Johannes Berg wrote:
> On Tue, 2019-05-14 at 17:01 +0800, Yibo Zhao wrote:
>> In multiple SSID cases, it takes time to prepare every AP interface
>> to be ready in initializing phase. If a sta already knows everything
>> it
>> needs to join one of the APs and sends authentication to the AP which
>> is not fully prepared at this point of time, AP's channel context
>> could be NULL. As a result, warning message occurs.
>>
> Err, what was the point in sending v2 without any changes?
>
> johannes
Hi Johannes,
I was planning to use WARN_ON_ONCE() in the first place to replace
WARN_ON() then after some discussion, we think removing it could be
better. So the first patch was based on my first version which is sent
incorrectly. Please check again.
Sorry for the confusing.
--
Yibo
next prev parent reply other threads:[~2019-05-14 9:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 9:01 [PATCH v2] mac80211: remove warning message Yibo Zhao
2019-05-14 9:01 ` Yibo Zhao
2019-05-14 9:05 ` Johannes Berg
2019-05-14 9:05 ` Johannes Berg
2019-05-14 9:10 ` Yibo Zhao [this message]
2019-05-14 9:10 ` Yibo Zhao
2019-05-14 9:12 ` Johannes Berg
2019-05-14 9:12 ` Johannes Berg
2019-05-14 15:44 ` Joe Perches
2019-05-14 15:44 ` Joe Perches
2019-05-14 17:55 ` Ben Greear
2019-05-14 17:55 ` Ben Greear
2019-05-14 18:40 ` Johannes Berg
2019-05-14 18:40 ` Johannes Berg
2019-05-14 18:54 ` Ben Greear
2019-05-14 18:54 ` Ben Greear
2019-05-14 18:57 ` Johannes Berg
2019-05-14 18:57 ` Johannes Berg
2019-05-20 13:56 ` Yibo Zhao
2019-05-20 13:56 ` Yibo Zhao
2019-06-14 2:52 ` Yibo Zhao
2019-06-14 2:52 ` Yibo Zhao
2019-06-14 7:22 ` Johannes Berg
2019-06-14 7:22 ` Johannes Berg
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=ccb48284f0d96e72f4c041e12c943f0a@codeaurora.org \
--to=yiboz@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=zhichen@codeaurora.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 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.