From: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
To: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
Cc: Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Joseph Fannin <jhf-rN3PHIWzTs1Jm/Hvfsr4+Q@public.gmane.org>,
Ray Lee <ray-lk-0Cg02Ec9UG4BXFe83j6qeQ@public.gmane.org>,
Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>,
bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: Re: RFC/T: Trial fix for the bcm43xx - wpa_supplicant - NetworkManager deadlock
Date: Tue, 21 Nov 2006 23:54:13 +0100 [thread overview]
Message-ID: <200611212354.13362.mb@bu3sch.de> (raw)
In-Reply-To: <200611210959.17644.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
> I put the equivalent into my system about 12 hours ago and have not seen any problems.
It's definately a bugfix and it should go into the
trees (stable too) after some regression testing, regardless of
whether this fixes _this_ bug or not.
PS: I had some MTA problems (caused by PEBCAK) and lost some
or today's mail. The server seems to have bounced.
I'm sorry for this.
So, if somebody sent me a mail in the last 9 hours, better resend. :)
Thanks.
--
Greetings Michael.
prev parent reply other threads:[~2006-11-21 22:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4561DBE0.2060908@lwfinger.net>
2006-11-21 5:17 ` RFC/T: Trial fix for the bcm43xx - wpa_supplicant - NetworkManager deadlock Ray Lee
2006-11-21 18:05 ` Larry Finger
2006-11-21 18:32 ` Johannes Berg
2006-11-21 18:36 ` Johannes Berg
2006-11-21 18:49 ` Larry Finger
2006-11-22 13:58 ` Dan Williams
2006-11-22 17:11 ` Ray Lee
[not found] ` <200611210017.47695.mb@bu3sch.de>
[not found] ` <1164098989.2769.9.camel@ux156>
2006-11-21 8:59 ` Michael Buesch
[not found] ` <200611210959.17644.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-11-21 16:30 ` Larry Finger
2006-11-21 22:54 ` Michael Buesch [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=200611212354.13362.mb@bu3sch.de \
--to=mb-fseuscv1ubazqb+pc5nmwq@public.gmane.org \
--cc=Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org \
--cc=bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jhf-rN3PHIWzTs1Jm/Hvfsr4+Q@public.gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ray-lk-0Cg02Ec9UG4BXFe83j6qeQ@public.gmane.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 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.