From: Florian Mickler <florian@mickler.org>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
"Berg, Johannes" <johannes.berg@intel.com>,
Zhu Yi <yi.zhu@intel.com>,
"Cahill, Ben M" <ben.m.cahill@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iwl3945: queue the right work if the scan needs to be aborted
Date: Mon, 27 Sep 2010 08:13:58 +0200 [thread overview]
Message-ID: <20100927081358.07b30327@schatten.dmk.lab> (raw)
In-Reply-To: <1285357868.12594.8.camel@wwguy-ubuntu>
On Fri, 24 Sep 2010 12:51:08 -0700
"Guy, Wey-Yi" <wey-yi.w.guy@intel.com> wrote:
> Hi Florian,
>
> Thanks for sending the patch, the scan operation in iwlwifi just being
> modified and the changes you have no longer apply.please check the
> latest kernel.
>
> Thanks
> Wey
>
Ok, I checked out
git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-2.6.git
and it definitely looks better in there. This patch shouldn't be
necessary for that.
Do you plan on submitting this for 2.6.36 or .37?
I think my patch should fix the instance reported in the bug in a less
invasive manner.
Only remaining question is why it did only show up now. But that's
probably due to the workqueue changes.
Regards,
Flo
next prev parent reply other threads:[~2010-09-27 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 16:22 [PATCH] iwl3945: queue the right work if the scan needs to be aborted Florian Mickler
2010-09-24 19:51 ` Guy, Wey-Yi
2010-09-27 6:13 ` Florian Mickler [this message]
2010-09-27 19:59 ` Guy, Wey-Yi W
2010-09-27 20:11 ` Guy, Wey-Yi
-- strict thread matches above, loose matches on Subject: below --
2010-10-05 6:43 Fw: " Florian Mickler
2010-10-05 8:57 ` Stanislaw Gruszka
2010-10-05 10:12 ` Florian Mickler
2010-10-05 10:43 ` Stanislaw Gruszka
2010-10-05 22:29 ` Florian Mickler
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=20100927081358.07b30327@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=ben.m.cahill@intel.com \
--cc=ilw@linux.intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=wey-yi.w.guy@intel.com \
--cc=yi.zhu@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).