From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stefano Brivio <st3-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>,
Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>,
Broadcom Linux
<bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org>
Subject: Re: [PATCH] fix for system lockups in 2.6.18-rcX caused by bcm43xx
Date: Sat, 9 Sep 2006 11:23:10 -0400 [thread overview]
Message-ID: <20060909152305.GA27080@tuxdriver.com> (raw)
In-Reply-To: <45021D4A.6040805-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
On Fri, Sep 08, 2006 at 08:47:54PM -0500, Larry Finger wrote:
> PLease send this upstream for inclusion in 2.6.18, if possible. This patch
> will not work for
> wireless-2.6. That patch will be sent to you soon.
Are you saying this will break the upstream branch of wireless-2.6?
I'm not too excited about that. Under the normal process, that would
mean 2.6.19 would be broken until we get the next patch.
When will the patch for the upstream branch be available? Can you make
that patch based on this one (i.e. apply this one before generating
the next patch)?
John
--
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
next prev parent reply other threads:[~2006-09-09 15:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-09 1:47 [PATCH] fix for system lockups in 2.6.18-rcX caused by bcm43xx Larry Finger
[not found] ` <45021D4A.6040805-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-09 15:23 ` John W. Linville [this message]
2006-09-09 16:04 ` Larry Finger
[not found] ` <4502E62B.5060601-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-09 19:42 ` Daniel Drake
2006-09-11 19:28 ` John W. Linville
2006-09-11 19:59 ` Larry Finger
[not found] ` <4505C005.2070302-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-09-11 20:35 ` John W. Linville
2006-09-11 22:04 ` Jeff Garzik
2006-09-14 8:25 ` Jarek Poplawski
2006-09-14 8:29 ` Jarek Poplawski
2006-10-05 20:52 ` Randy Dunlap
2006-10-06 5:57 ` Jarek Poplawski
2006-10-06 6:19 ` Jarek Poplawski
2006-10-06 6:57 ` Jarek Poplawski
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=20060909152305.GA27080@tuxdriver.com \
--to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
--cc=Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org \
--cc=bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=st3-sGOZH3hwPm2sTnJN9+BGXg@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 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).