From: Arend van Spriel <arend@broadcom.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>, Felix Fietkau <nbd@openwrt.org>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Subject: Re: Bumping required kernels to 3.0 for Linux backports ?
Date: Wed, 9 Apr 2014 12:59:35 +0200 [thread overview]
Message-ID: <53452817.5060502@broadcom.com> (raw)
In-Reply-To: <CAB=NE6VvyBKzEg=ErZzQMktY8eLytQ21JCPrOQbxvZ9m-nqHkw@mail.gmail.com>
On 09/04/14 03:03, Luis R. Rodriguez wrote:
> Folks,
>
[...]
> To start off -- what's the *last* kernel you realistically need for
> your users to use backports right now? Is it really 2.6.25? Would
> anyone kick and scream if for the backports-3.15 release try take
> things up to support only down to least 3.0 *right now* ?
A lot of test teams in broadcom wlan are still using Fedora 15 running a
2.6.38 kernel. We are pushing them to move to Fedora 19.
Regards,
Arend
> [0] http://www.do-not-panic.com/2014/04/automatic-linux-kernel-backporting-with-coccinelle.html
>
> Luis
> --
> To unsubscribe from this list: send the line "unsubscribe backports" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-04-09 10:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 1:03 Bumping required kernels to 3.0 for Linux backports ? Luis R. Rodriguez
2014-04-09 9:18 ` Felix Fietkau
2014-04-09 18:28 ` Luis R. Rodriguez
2014-04-09 19:12 ` Greg Kroah-Hartman
2014-04-09 20:01 ` Luis R. Rodriguez
2014-04-09 20:22 ` Greg Kroah-Hartman
2014-04-09 20:52 ` Luis R. Rodriguez
2014-04-09 21:06 ` Greg Kroah-Hartman
2014-04-10 7:31 ` Johannes Berg
2014-04-10 7:44 ` Takashi Iwai
2014-04-10 16:59 ` Luis R. Rodriguez
2014-04-10 17:04 ` Arend van Spriel
2014-04-10 17:11 ` Luis R. Rodriguez
2014-04-10 18:56 ` Luis R. Rodriguez
2014-04-11 7:51 ` Arend van Spriel
2014-04-11 18:18 ` Luis R. Rodriguez
2014-04-10 17:16 ` Johannes Berg
2014-04-10 17:26 ` Felix Fietkau
2014-04-10 17:35 ` Johannes Berg
2014-04-09 10:59 ` Arend van Spriel [this message]
2014-04-09 18:25 ` Luis R. Rodriguez
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=53452817.5060502@broadcom.com \
--to=arend@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=mcgrof@do-not-panic.com \
--cc=nbd@openwrt.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