From: Larry Finger <Larry.Finger@lwfinger•net>
To: "John W. Linville" <linville@tuxdriver•com>
Cc: netdev@vger•kernel.org, Michael Buesch <mb@bu3sch•de>,
Stefano Brivio <st3@riseup•net>,
Broadcom Linux <bcm43xx-dev@lists•berlios.de>
Subject: Re: [PATCH] fix for system lockups in 2.6.18-rcX caused by bcm43xx
Date: Sat, 09 Sep 2006 11:04:59 -0500 [thread overview]
Message-ID: <4502E62B.5060601@lwfinger.net> (raw)
In-Reply-To: <20060909152305.GA27080@tuxdriver.com>
John W. Linville wrote:
> 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)?
It will not break wireless-2.6. I sent the equivalent of this patch for wireless-2.6 to you under
the subject "[PATCH] bcm43xx-softmac: Init, shutdown and restart fixes" on August 21, just after I
took over maintenance of bcm43xx-softmac. If this is not currently queued, please let me know. There
is still a problem with one section of the code touched by that patch that is related to a
synchronize_net() call. Michael and I are trying to get a network guru to answer some questions
regarding that function. So far no response to our pleas.
I would like to get a listing of patches for bcm43xx-softmac that are queued but not yet applied,
and the order in which they will be applied. I want to make sure nothing has fallen through the
cracks, and that the patches will apply cleanly.
Thanks,
Larry
next prev parent reply other threads:[~2006-09-09 16:05 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
2006-09-09 16:04 ` Larry Finger [this message]
[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=4502E62B.5060601@lwfinger.net \
--to=larry.finger@lwfinger$(echo .)net \
--cc=bcm43xx-dev@lists$(echo .)berlios.de \
--cc=linville@tuxdriver$(echo .)com \
--cc=mb@bu3sch$(echo .)de \
--cc=netdev@vger$(echo .)kernel.org \
--cc=st3@riseup$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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