From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: gregkh@suse.de, devel@linuxdriverproject.org,
linux-wireless@vger.kernel.org, vmehta@atheros.com,
naveen.singh@atheros.com, stable@kernel.org,
Naveen Singh <nsingh@atheros.com>,
Wey-Yi Guy <wey-yi.w.guy@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>
Subject: Re: [RTF] iwmc3200wifi: fix device registration ordering for cfg80211
Date: Fri, 18 Mar 2011 09:50:58 -0400 [thread overview]
Message-ID: <20110318135058.GE5103@tuxdriver.com> (raw)
In-Reply-To: <AANLkTi=58JJNoYG7232ykiOnAK2TX18ROxrfYQir3Wwe@mail.gmail.com>
On Thu, Mar 17, 2011 at 08:11:17PM -0700, Luis R. Rodriguez wrote:
> On Thu, Mar 17, 2011 at 8:10 PM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
> > Without this you can get a race against udev and userspace daemons
> > which will try to poke the device even before netdev ops and friends
> > are available. Device initialization will fail without this.
> >
> > Cc: stable@kernel.org
> > Cc: Naveen Singh <nsingh@atheros.com>
> > Cc: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> > Cc: Intel Linux Wireless <ilw@linux.intel.com>
> > Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
> > ---
>
> Oops sorry, this was supposed to go to Linville.
And probably "[RFT]" instead of "[RTF]" too. :-)
Does anyone even have this hardware?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-03-18 14:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 3:10 [RTF] iwmc3200wifi: fix device registration ordering for cfg80211 Luis R. Rodriguez
2011-03-18 3:11 ` Luis R. Rodriguez
2011-03-18 13:50 ` John W. Linville [this message]
2011-03-18 16:05 ` Luis R. Rodriguez
2011-03-18 17:41 ` Luis R. Rodriguez
2011-03-18 18:03 ` Johannes Berg
2011-03-18 18:05 ` Luis R. Rodriguez
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=20110318135058.GE5103@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=naveen.singh@atheros.com \
--cc=nsingh@atheros.com \
--cc=stable@kernel.org \
--cc=vmehta@atheros.com \
--cc=wey-yi.w.guy@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 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.