From: "John W. Linville" <linville@tuxdriver.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: Jeff Garzik <jeff@garzik.org>,
Andrew Morton <akpm@linux-foundation.org>,
Gary Zambrano <zambrano@broadcom.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
bcm43xx-dev@lists.berlios.de, ralf@linux-mips.org,
davej@codemonkey.org.uk, mtakahashi@kanno.co.jp
Subject: Re: Merging SSB upstream
Date: Sun, 6 May 2007 13:38:33 -0400 [thread overview]
Message-ID: <20070506173833.GA4717@tuxdriver.com> (raw)
In-Reply-To: <200705061144.27817.mb@bu3sch.de>
On Sun, May 06, 2007 at 11:44:27AM +0200, Michael Buesch wrote:
> On Sunday 06 May 2007 04:00:51 John W. Linville wrote:
> > I had to remove
> > the b44 ssb changes from fedora because a) users reported problems;
>
> Which problems were that? The 2 compile issues?
> Trivial to fix if that's the only issue. ;)
I knew you would ask that... :-)
I don't think there was a bugzilla, but Dave Jones forwarded an email
to me from "MASAO TAKAHASHI" in late February. Takahashi-san (forgive
me if I did that wrong) was complaining about tx timeouts after I
had added the full wireless-dev patchset to rawhide. Removing the
b44 bits of the patch seemed to remove the problem.
That's all the info I have. Perhaps Dave or Takahashi-san can add
to the description?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-05-06 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 1:03 Merging SSB upstream Michael Buesch
2007-05-06 1:03 ` Michael Buesch
2007-05-06 2:00 ` John W. Linville
2007-05-06 2:00 ` John W. Linville
2007-05-06 9:44 ` Michael Buesch
2007-05-06 9:44 ` Michael Buesch
2007-05-06 17:38 ` John W. Linville [this message]
2007-05-06 18:44 ` Michael Buesch
2007-05-06 18:44 ` Michael Buesch
2007-05-06 3:11 ` Jeff Garzik
2007-05-06 3:11 ` Jeff Garzik
2007-05-06 9:41 ` Michael Buesch
2007-05-07 16:43 ` Gary Zambrano
2007-05-07 16:43 ` Gary Zambrano
2007-05-07 20:35 ` Michael Buesch
2007-05-07 20:35 ` 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=20070506173833.GA4717@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@linux-foundation.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=davej@codemonkey.org.uk \
--cc=jeff@garzik.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=mtakahashi@kanno.co.jp \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=zambrano@broadcom.com \
/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.