All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	Felix Fietkau <nbd@openwrt.org>,
	"backports@vger.kernel.org" <backports@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jiri Slaby <jslaby@suse.cz>,
	Mauro Carvalho Chehab <m.chehab@samsung.com>
Subject: Re: Bumping required kernels to 3.0 for Linux backports ?
Date: Thu, 10 Apr 2014 09:31:26 +0200	[thread overview]
Message-ID: <1397115086.4757.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20140409210613.GA14392@kroah.com> (sfid-20140409_230344_484222_1B571B0F)

On Wed, 2014-04-09 at 14:06 -0700, Greg Kroah-Hartman wrote:

> Why 3.0?  That's not supported by anyone anymore for "new hardware", I'd
> move to 3.2 if you could, as that's the Debian stable release that will
> be maintained for quite some time yet:
> 	https://www.kernel.org/category/releases.html

We still need 3.0 for an ongoing project.

johannes


  reply	other threads:[~2014-04-10  7:31 UTC|newest]

Thread overview: 32+ 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 [this message]
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 17:24                     ` Loren Kirkby
2014-04-10 17:25                     ` Loren Kirkby
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-11 14:22                   ` Harrison Lee
2014-04-11 18:23                     ` Luis R. Rodriguez
2014-04-11 18:45                       ` Johannes Berg
2014-04-11 19:18                         ` Luis R. Rodriguez
2014-04-11 19:51                           ` Harrison Lee
2014-04-11 19:56                             ` Luis R. Rodriguez
2014-04-11 20:07                           ` Johannes Berg
2014-04-11 20:47                             ` Luis R. Rodriguez
2014-04-11 19:26                         ` Solomon Peachy
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
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=1397115086.4757.2.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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 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.