All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Please pull 'libertas-upstream' branch of wireless-2.6
Date: Tue, 07 Aug 2007 18:22:59 -0400	[thread overview]
Message-ID: <46B8F0C3.6030409@garzik.org> (raw)
In-Reply-To: <20070806203005.GL6442@tuxdriver.com>

John W. Linville wrote:
> Got a big patch bomb from the libertas guys.  I tried to cherry-pick
> some of the fixes for 2.6.23, but they either were fixes to problems
> in new code or all the code cleanups made them difficult for me to
> intelligently backport.
> 
> So, this is intended for 2.6.24...
> 
> ---
> 
> The following changes since commit d4ac2477fad0f2680e84ec12e387ce67682c5c13:
>   Linus Torvalds (1):
>         Linux 2.6.23-rc2
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git libertas-upstream

This is missing the patch.  I looked at it locally, but please do send a 
patch for review with each push, no matter how big.

pulled into #upstream



  parent reply	other threads:[~2007-08-07 22:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 20:30 Please pull 'libertas-upstream' branch of wireless-2.6 John W. Linville
2007-08-06 22:10 ` Dan Williams
2007-08-07 22:22 ` Jeff Garzik [this message]
2007-08-08  0:50   ` John W. Linville
     [not found] <20070529183347.GD3496@tuxdriver.com>
     [not found] ` <20070612210544.GF310@tuxdriver.com>
2007-06-12 21:06   ` Please pull 'libertas-fixes' " John W. Linville
2007-06-12 21:08     ` Please pull 'libertas-upstream' " John W. Linville
2007-06-13 19:57       ` 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=46B8F0C3.6030409@garzik.org \
    --to=jeff@garzik.org \
    --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 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.