From: reinette chatre <reinette.chatre@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: fix deferred hardware scan requests
Date: Tue, 02 Feb 2010 13:41:41 -0800 [thread overview]
Message-ID: <1265146901.2551.1407.camel@rchatre-DESK> (raw)
In-Reply-To: <1265140183.29119.82.camel@johannes.local>
Hi Johannes,
On Tue, 2010-02-02 at 11:49 -0800, Johannes Berg wrote:
> I was able to reproduce the problem, and the following seems to fix it
> for me; what do you think?
Thank you very much. This looks good, much cleaner. The code touched
here changed since 2.6.33 ... could you please create a 2.6.33 version
also?
Reinette
next prev parent reply other threads:[~2010-02-02 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 18:54 [PATCH] mac80211: fix deferred hardware scan requests Reinette Chatre
2010-02-02 18:54 ` [PATCH v2.6.33] " Reinette Chatre
2010-02-02 19:49 ` [PATCH] " Johannes Berg
2010-02-02 21:41 ` reinette chatre [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-03 9:21 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=1265146901.2551.1407.camel@rchatre-DESK \
--to=reinette.chatre@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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