From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: jeff@garzik.org, netdev@vger.kernel.org, gregkh@suse.de,
linux-wireless@vger.kernel.org,
linux-usb-users@lists.sourceforge.net, mb@bu3sch.de,
zambrano@broadcom.com
Subject: Re: Please pull 'ssb-drivers' branch of wireless-2.6
Date: Wed, 19 Sep 2007 17:27:56 -0400 [thread overview]
Message-ID: <20070919212756.GA3136@tuxdriver.com> (raw)
In-Reply-To: <20070919.142529.03110023.davem@davemloft.net>
On Wed, Sep 19, 2007 at 02:25:29PM -0700, David Miller wrote:
> From: "John W. Linville" <linville@tuxdriver.com>
> Date: Wed, 19 Sep 2007 16:44:28 -0400
> > The second patch adds a driver for a USB OHCI device which lives on
> > the SSB bus. Again, this is found on a number of SoC devices used
> > especially in wireless routers and APs.
> I'll let Greg take in the OHCI thing. I would suggest that he
> queue it up, and then once I get the net-2.6.24 tree into the
> merge window (which contains the SSB stack) he can push the
> OHCI change in afterwards.
ACK
--
John W. Linville
linville@tuxdriver.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Linux-usb-users@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
next prev parent reply other threads:[~2007-09-19 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 20:44 Please pull 'ssb-drivers' branch of wireless-2.6 John W. Linville
2007-09-19 21:25 ` David Miller
2007-09-19 21:27 ` John W. Linville [this message]
[not found] ` <20070919204428.GE5483-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-09-19 21:33 ` Greg KH
[not found] ` <20070919213356.GB15510-l3A5Bk7waGM@public.gmane.org>
2007-09-20 13:19 ` John W. Linville
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=20070919212756.GA3136@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=jeff@garzik.org \
--cc=linux-usb-users@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.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 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).