netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
	mb@bu3sch.de, bunk@stusta.de, netdev@vger.kernel.org,
	akpm@linux-foundation.org
Subject: Re: SSB/b44 build failure
Date: Sat, 10 Mar 2007 18:05:42 +0000	[thread overview]
Message-ID: <20070310180541.GA17160@infradead.org> (raw)
In-Reply-To: <20070310150346.GB5062@tuxdriver.com>

On Sat, Mar 10, 2007 at 10:03:46AM -0500, John W. Linville wrote:
> FWIW, this is coming from the port of b44 to use the SSB bus which
> I'm carrying in the wireless-dev tree.
> >
> SSB (i.e. "Sonics Silicon Backplane") is a bus used in Broadcom SoCs
> including the b44 and bcm43xx hardware.  The SSB bus driver and the
> b44 port to SSB is being developed by Michael Buesch, the maintainer of
> the bcm43xx driver.  I've been carrying the b44 SSB port in my tree for
> Michael's convenience.  Just an FYI for those wondering what SSB is...

Btw, what's the reason this is in wireless-dev?  Could we please merge
this code into mainline soonish (aka 2.6.22) instead of interwinding
it with totally unrelated wireless changes?


  parent reply	other threads:[~2007-03-10 18:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-10  3:14 SSB/b44 build failure Randy Dunlap
2007-03-10 15:03 ` John W. Linville
2007-03-10 15:38   ` Adrian Bunk
2007-03-10 16:22     ` John W. Linville
2007-03-11 17:22       ` Adrian Bunk
2007-03-10 17:33     ` Michael Buesch
2007-03-10 18:05   ` Christoph Hellwig [this message]
2007-03-10 19:27     ` 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=20070310180541.GA17160@infradead.org \
    --to=hch@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@stusta.de \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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).