linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kunal Gangakhedkar <kunal.gangakhedkar@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: tim.gardner@canonical.com,
	"linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: Stable compat-wireless 2.6.32-rc4 released
Date: Thu, 15 Oct 2009 11:26:04 +0530	[thread overview]
Message-ID: <200910151126.04423.kunal.gangakhedkar@gmail.com> (raw)
In-Reply-To: <43e72e890910140734j196a06f2y8905d3eb1ba1abc8@mail.gmail.com>

On Wednesday 14 Oct 2009 8:04:32 pm Luis R. Rodriguez wrote:
> On Tue, Oct 13, 2009 at 11:01 PM, Kunal Gangakhedkar
>
> <kunal.gangakhedkar@gmail.com> wrote:
> > On Wednesday 14 Oct 2009 6:20:33 am Luis R. Rodriguez wrote:
> >> On Tue, Oct 13, 2009 at 5:25 PM, Tim Gardner <tim.gardner@canonical.com>
> >
> > wrote:
> >> > Speaking as a distro, what advantage does the stable wireless backport
> >> > offer for the currently released kernel if we are already consumers of
> >> > stable updates?
> >>
> >> Well if you are a distro stuck on the 2.6.31 kernel the stable
> >> compat-wireless-2.6.32 gets you 2.6.32 wireless bits on 2.6.31 and
> >> that means any features/drivers/large fixes/enhancements that didn't
> >> make it to 2.6.31.
> >
> > Isn't this the whole purpose of linux-backports-modules in ubuntu as
> > well?
>
> Yes, but lbm currently relies on the bleeding edge compat-wireless
> which is exactly that -- bleeding edge, it may or may not work. The
> stable compat-wireless releases are based on the latest stable kernel
> releases and latest rc kernel release so they are deemed to be stable
> snapshots following the kernel release cycle.
>
>   Luis

Got that - thanks for the explanation :)

Kunal

      parent reply	other threads:[~2009-10-15  5:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-13 22:42 Stable compat-wireless 2.6.32-rc4 released Luis R. Rodriguez
2009-10-14  0:25 ` Tim Gardner
2009-10-14  0:50   ` Luis R. Rodriguez
2009-10-14  6:01     ` Kunal Gangakhedkar
2009-10-14 14:34       ` Luis R. Rodriguez
2009-10-14 15:26         ` Tim Gardner
2009-10-14 16:51           ` Luis R. Rodriguez
2009-10-15  5:56         ` Kunal Gangakhedkar [this message]

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=200910151126.04423.kunal.gangakhedkar@gmail.com \
    --to=kunal.gangakhedkar@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=tim.gardner@canonical.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).