lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAB=NE6WPm+as8x7+MEpm9E_jWffZuOe6yzYoiLFowLMroWn=bA@mail.gmail.com>
Date:	Fri, 11 Apr 2014 11:18:30 -0700
From:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	Takashi Iwai <tiwai@...e.de>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Felix Fietkau <nbd@...nwrt.org>,
	"backports@...r.kernel.org" <backports@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Jiri Slaby <jslaby@...e.cz>,
	Mauro Carvalho Chehab <m.chehab@...sung.com>
Subject: Re: Bumping required kernels to 3.0 for Linux backports ?

On Fri, Apr 11, 2014 at 12:51 AM, Arend van Spriel <arend@...adcom.com> wrote:
> That was 2 years ago when you asked me ;-) Since then I have been using it
> to backport the brcm80211 mainline drivers to 1) Android kernel, ie. 3.4
> kernel, and 2) Fedora 19 which is actually fixed to 3.11 kernel.
>
> So we use backports these days for enabling brcm80211 drivers on various
> test equipment that uses older kernels.

Neat! All the kernels seem covered, what stuff was using the older
stuff and can those not be moved to newer kernels ?

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ