From: Michael Buesch <mb@bu3sch.de>
To: linville@tuxdriver.com, Jiri Benc <jbenc@suse.cz>
Cc: bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] d80211: make sleeping in hw->config possible #2
Date: Wed, 12 Jul 2006 22:34:44 +0200 [thread overview]
Message-ID: <200607122234.44309.mb@bu3sch.de> (raw)
In-Reply-To: <20060712185331.0573b1b1@griffin.suse.cz>
On Wednesday 12 July 2006 18:53, Jiri Benc wrote:
> On Tue, 11 Jul 2006 00:54:33 +0200, Michael Buesch wrote:
> > Please apply this to wireless-dev.
> > Note that this is the second try to submit this patch.
> > The first try contained a little bug. I'm sorry for that.
> > If you already applied the first one, I can provide an incremental patch.
> >
> > Note2 that this patch depends on the
> > [PATCH] cancel_rearming_delayed_work infinite loop fix
> > I just sent out to the lists and akpm.
>
> I'm still digging through this. But I think it is not necessary to use
> cancel_rearming_delayed_work at all; will try to make a patch.
Jiri, so you care to get that patch upstream?
Would be cool, thanks.
John, do you manage to apply the bcm43xx init fix patch, which
depends on this one, to the tree after this one got in?
Or should I resend it?
--
Greetings Michael.
next prev parent reply other threads:[~2006-07-12 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 22:54 [PATCH] d80211: make sleeping in hw->config possible #2 Michael Buesch
2006-07-11 4:25 ` Andrew Morton
2006-07-11 9:11 ` Michael Buesch
2006-07-11 9:31 ` Andrew Morton
2006-07-11 10:12 ` Michael Buesch
2006-07-12 16:53 ` Jiri Benc
2006-07-12 20:34 ` Michael Buesch [this message]
2006-07-18 16:57 ` [RFC, RFT] " Jiri Benc
[not found] ` <20060718185711.21aaf55b-IhiK2ZEFs2oCVLCxKZUutA@public.gmane.org>
2006-07-18 17:36 ` Michael Buesch
2006-07-18 17:58 ` Michael Buesch
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=200607122234.44309.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@osdl.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--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).