public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: 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: Wed, 9 Apr 2014 12:12:25 -0700	[thread overview]
Message-ID: <20140409191225.GA10560@kroah.com> (raw)
In-Reply-To: <CAB=NE6UUN4vQd3SpsvO5tcgaYq3YXQeE0KtZGki7p7OnR=J4RA@mail.gmail.com>

On Wed, Apr 09, 2014 at 11:28:55AM -0700, Luis R. Rodriguez wrote:
> On Wed, Apr 9, 2014 at 2:18 AM, Felix Fietkau <nbd@openwrt.org> wrote:
> > The oldest kernel in OpenWrt that we're still supporting with updates of
> > the backports tree is 3.3, so raising the minimum requirement to 3.0 is
> > completely fine with me.
> 
> OK note that 3.3 is not listed on kernel.org as supported. I'm fine in
> carrying the stuff for those for now but ultimately it'd also be nice
> if we didn't even have to test the kernels in between which are not
> listed. This does however raise the question of how often a kernel in
> between a list of supported kernels gets picked up to be supported
> eventually. Greg, Jiri, do you happen to know what the likelyhood of
> that can be?

I don't know of anything ever getting picked up after I have said it
would not be supported anymore.

thanks,

greg k-h

  reply	other threads:[~2014-04-09 19:09 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 [this message]
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
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=20140409191225.GA10560@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=backports@vger.kernel.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