From: Tim Gardner <tim.gardner@canonical.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Greg KH <greg@kroah.com>
Subject: Re: Stable compat-wireless 2.6.32-rc4 released
Date: Tue, 13 Oct 2009 18:25:32 -0600 [thread overview]
Message-ID: <4AD51A7C.9060207@canonical.com> (raw)
In-Reply-To: <43e72e890910131542k376a87c5rc30feb6491a06867@mail.gmail.com>
Luis R. Rodriguez wrote:
> As the kernel moves along so does the automatic stable backports for
> the wireless subsystem [1]. We are now on 2.6.32-rc4. Besides getting
> the same fixes from rc1..rc4 some backport changes were made as well,
> most importantly that of relying on your own kernel's iw_handler.h.
> I've tested this release with 2.6.28.
>
> Please report any issues you see.
>
> [1] http://wireless.kernel.org/en/users/Download/stable
>
> PS. If you maintain a distribution and rely on stable compat-wireless
> releases please let me know so I can CC you when further updates are
> made.
>
> Luis
>
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?
rtg
--
Tim Gardner tim.gardner@canonical.com
next prev parent reply other threads:[~2009-10-14 0:26 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 [this message]
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
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=4AD51A7C.9060207@canonical.com \
--to=tim.gardner@canonical.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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 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.