linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	linux-wireless@vger.kernel.org
Subject: Re: Please pull 'upstream-jgarzik' branch of wireless-2.6
Date: Tue, 04 Dec 2007 15:13:19 -0500	[thread overview]
Message-ID: <4755B4DF.10803@garzik.org> (raw)
In-Reply-To: <20071204135925.GB19911@tuxdriver.com>

John W. Linville wrote:
> Jeff,
> 
> Here are more than 5 score patches intended for 2.6.25.  This request
> replaces the request sent on 27 November. [1]
> 
> There are tons of updates here, especially iwlwifi and libertas.  The
> b43, b43legacy, rt2x00, rtl8187, and zd1211rw drivers are also updated.
> 
> This pull contains the port of zd1211rw to the mac80211 infrastructure.
> There is also some SSB stuff in there.  I've been sending that stuff
> to Dave M., but since later b43 patches depend on it I thought it
> would be better to send them your way.  I'll CC Dave.
> 
> Also included is the iwl4965 work to use the .11n stuff that has been
> added in the net-2.6.25 tree.  For now I've added a "depends on n" to
> the IWL4965_HT Kconfig to avoid build breakage in your tree.
> 
> The total diff is getting big -- the patch is nearing 2MB.  Please let
> me know if there are any problems so we can get (at least some of)
> this merged!
> 
> Thanks,
> 
> John
> 
> [1] http://marc.info/?l=linux-netdev&m=119617493212177&w=2
> 
> ---
> 
> Individual patches are available here:
> 
> 	http://www.kernel.org/pub/linux/kernel/people/linville/wireless-2.6/upstream-jgarzik
> 
> ---
> 
> The following changes since commit e86d91426d8b3d79010c9d5c617d7594e5c165aa:
>   Jeff Garzik (1):
>         Merge branch 'r6040' of git://git.kernel.org/.../romieu/netdev-2.6 into upstream
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git upstream-jgarzik

pulled



  reply	other threads:[~2007-12-04 20:13 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04 13:59 Please pull 'upstream-jgarzik' branch of wireless-2.6 John W. Linville
2007-12-04 20:13 ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-08 22:23 John W. Linville
2007-12-20 15:54 John W. Linville
2007-12-16  4:34 John W. Linville
2007-12-17 23:24 ` Jeff Garzik
2007-12-17 23:40   ` Jeff Garzik
2007-12-18  1:24     ` Zhu Yi
2007-11-27 14:47 John W. Linville
2007-11-27 16:08 ` Holger Schurig
2007-11-27 16:12   ` Dan Williams
2007-11-28  7:25     ` Holger Schurig
2007-11-27 18:55   ` John W. Linville
2007-12-04 13:55 ` John W. Linville
2007-11-06  1:16 John W. Linville
2007-11-06 17:43 ` Jeff Garzik
2007-09-15 13:21 John W. Linville
2007-09-18  1:54 ` Zhu Yi
2007-08-28 23:17 John W. Linville
2007-08-31 13:44 ` Jeff Garzik
2007-08-15  0:36 John W. Linville
2007-08-25  6:40 ` Jeff Garzik
2007-08-06 20:14 Please pull 'fixes-jgarzik' " John W. Linville
2007-08-06 20:16 ` Please pull 'upstream-jgarzik' " John W. Linville
2007-08-07 22:21   ` Jeff Garzik
2007-07-18  2:19 John W. Linville
2007-07-18 22:31 ` Jeff Garzik
2007-07-10 18:57 John W. Linville
2007-07-16 21:59 ` Jeff Garzik

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=4755B4DF.10803@garzik.org \
    --to=jeff@garzik.org \
    --cc=davem@davemloft.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.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).