mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: linux-wireless <linux-wireless@vger.kernel.org>,
	linux-bluetooth <linux-bluetooth@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compat-wireless for 2.6.34 - 802.11 and bluetooth backported
Date: Mon, 12 Apr 2010 22:35:06 -0700	[thread overview]
Message-ID: <v2q43e72e891004122235p87e971c9o12986a064f7d2be1@mail.gmail.com> (raw)
In-Reply-To: <m2s43e72e891004122151n2677a158o7f9aa8d054bf058e@mail.gmail.com>

On Mon, Apr 12, 2010 at 9:51 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
> We're up to 2.6.34-rc4 upstream but we hadn't released a respective
> compat-wireless stable [1] tarball yet. I finally got some time so
> just posted one up [2], this gives us the 2.6.34-rc4 wireless
> subsystem, bluetooth subsystem and new wireless/bluetooth drivers
> compilable and installed on older kernels. Please report any issues
> ASAP. For details on changes you can refer to the
> ChangeLog-2.6.34-rc4-wireless [3].
>
> I only did a quick build test against 2.6.31 and it seems to compile
> fine :), more compile tests reports against older kernels and actual
> loading tests reports against different kernels are greatly
> appreciated.
>
>  Luis
>
> [1] http://wireless.kernel.org/en/users/Download/stable
> [2] http://www.orbit-lab.org/kernel/compat-wireless-2.6-stable/v2.6.34/compat-wireless-2.6.34-rc4.tar.bz2
> [3] http://www.orbit-lab.org/kernel/compat-wireless-2.6-stable/v2.6.34/ChangeLog-2.6.34-rc4-wireless

Also just updated the tarballs for 2.6.32.11 and 2.6.33.2, and removed
the 2.6.30 and 2.6.31 tarballs since not even kernel.org supports
those anymore.

  Luis

      reply	other threads:[~2010-04-13  5:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13  4:51 Luis R. Rodriguez
2010-04-13  5:35 ` Luis R. Rodriguez [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=v2q43e72e891004122235p87e971c9o12986a064f7d2be1@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@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

all inboxes | Powered by JetHome®