netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Please pull 'libertas' branch of wireless-2.6
Date: Thu, 31 May 2007 17:16:05 -0400	[thread overview]
Message-ID: <20070531211605.GA30161@tuxdriver.com> (raw)
In-Reply-To: <1180645997.18078.8.camel@xo-28-0B-88.localdomain>

On Thu, May 31, 2007 at 05:13:17PM -0400, Dan Williams wrote:
> On Wed, 2007-05-30 at 11:28 -0400, Dan Williams wrote:
> > On Wed, 2007-05-30 at 10:07 -0400, Jeff Garzik wrote:
> > > John W. Linville wrote:
> > > > Lots of stuff here...probably best for 2.6.23...
> > > 
> > > Is this best for Linux users... or just easy for developers?
> > > 
> > > Won't putting off all these fixes until 2.6.23 leave the driver released 
> > > in 2.6.22 in shoddy shape?

> > If you think all the bits from this should just go to 2.6.22, that's
> > fine with me.  But I don't feel comfortable making that call given what
> > I thought were the constraints on pushing changes through during an rc
> > cycle.  When the merge window was open, we backported critical bug fixes
> > and necessary merge-requirement cleanups to the code in linville's tree,
> > but avoided changes that didn't impact function.
> 
> Any response on these points yet?  I've got yet more cleanups and a few
> other things queued in libertas-2.6 but I'd like to see where this
> discussion goes before sending a pull request for the new bits.

As for me, I have no great problem w/ the whole batch going to 2.6.22.
The driver is still new and most acknowledge it still has significant
defficiencies.  Most (but probably not all) of the patches would seem
to fit some definition of bug fix anyway.  I was just trying to err
on the side of caution and follow the normal "bugfixes in -rc" process.

Jeff, the branch in question is based off a vanilla 2.6.22-rc3.
So it is safe to pull (from a "won't mess-up my tree" perspective)
if you are so inclined.

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2007-05-31 22:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 18:33 Please pull 'libertas' branch of wireless-2.6 John W. Linville
     [not found] ` <20070529183347.GD3496-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-05-30 14:07   ` Jeff Garzik
2007-05-30 15:28     ` Dan Williams
     [not found]       ` <1180538928.17163.10.camel-Hs+VJEcF3DojzQS9c19i8iZi+YwRKgec@public.gmane.org>
2007-05-31 21:13         ` Dan Williams
2007-05-31 21:16           ` John W. Linville [this message]
     [not found]             ` <20070531211605.GA30161-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-06-01 21:48               ` Dan Williams
2007-06-12 21:05 ` John W. Linville
2007-06-12 21:06   ` Please pull 'libertas-fixes' " John W. Linville
     [not found]     ` <20070612210658.GG310-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-06-12 21:08       ` Please pull 'libertas-upstream' " John W. Linville
     [not found]         ` <20070612210814.GH310-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-06-13 19:57           ` Jeff Garzik
2007-06-12 22:54       ` Please pull 'libertas-fixes' " Jeff Garzik
2007-06-13  0:03         ` John W. Linville
2007-06-13  2:28       ` Jeff Garzik
     [not found]   ` <20070612210544.GF310-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-06-12 21:26     ` Please pull 'libertas' branch of wireless-2.6 (resent w/o attachment) John W. Linville
2007-06-13  2:28       ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2007-05-11 19:26 Please pull 'libertas' branch of wireless-2.6 John W. Linville
     [not found] ` <20070511192604.GC3474-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-05-11 20: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=20070531211605.GA30161@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=dcbw@redhat.com \
    --cc=jeff@garzik.org \
    --cc=linux-wireless@vger.kernel.org \
    --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).