From: Johannes Berg <johannes@sipsolutions.net>
To: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wireless: core: Reorder wiphy_register() notifications relevantly
Date: Fri, 15 Aug 2014 15:03:45 +0200 [thread overview]
Message-ID: <1408107825.15705.3.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1407935091-28516-1-git-send-email-tomasz.bursztyka@linux.intel.com> (sfid-20140813_150457_552550_15CAEAC1)
Subject should say cfg80211.
On Wed, 2014-08-13 at 16:04 +0300, Tomasz Bursztyka wrote:
> Currently it can send regulatory domain change notification before any
> NEW_WIPHY notification. Moreover, if rfill_register() fails, calling
> wiphy_unregister() will send a DEL_WIPHY though no NEW_WIPHY had been
> sent previously.
>
> Thus reordering so it properly notifies NEW_WIPHY before any other.
This also isn't actually true - now rfkill is *after* NEW_WIPHY.
This code had a bunch of sequencing issues in the past - please look
through the history and check that this doesn't re-introduce any of
them.
johannes
next prev parent reply other threads:[~2014-08-15 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 13:04 [PATCH] wireless: core: Reorder wiphy_register() notifications relevantly Tomasz Bursztyka
2014-08-15 13:03 ` Johannes Berg [this message]
2014-08-18 7:23 ` Tomasz Bursztyka
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=1408107825.15705.3.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasz.bursztyka@linux.intel.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;
as well as URLs for NNTP newsgroup(s).