From: Jiri Benc <jbenc@suse.cz>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: netdev@vger.kernel.org, Jan Kiszka <jan.kiszka@web.de>
Subject: Re: [PATCH] d80211: ieee80211_hw handlers should be allowed to sleep
Date: Thu, 19 Oct 2006 18:01:17 +0200 [thread overview]
Message-ID: <20061019180117.4833ee4d@griffin.suse.cz> (raw)
In-Reply-To: <200610181927.37471.IvDoorn@gmail.com>
On Wed, 18 Oct 2006 19:27:37 +0200, Ivo van Doorn wrote:
> Would something like the patch below be better?
> It keeps the flush_scheduled_work() at the same location, but a second
> is added in case local->scan_work.data != sdata->dev
Applied to my tree, thanks for the patch!
Jiri
--
Jiri Benc
SUSE Labs
prev parent reply other threads:[~2006-10-19 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-07 9:23 [PATCH] d80211: ieee80211_hw handlers should be allowed to sleep Ivo van Doorn
2006-10-18 13:06 ` Jiri Benc
2006-10-18 17:27 ` Ivo van Doorn
2006-10-18 18:10 ` Jan Kiszka
2006-10-19 16:01 ` Jiri Benc [this message]
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=20061019180117.4833ee4d@griffin.suse.cz \
--to=jbenc@suse.cz \
--cc=ivdoorn@gmail.com \
--cc=jan.kiszka@web.de \
--cc=netdev@vger.kernel.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 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).