From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: Harrison Lee <harrisonl@tme-inc.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: Bumping required kernels to 3.0 for Linux backports ?
Date: Fri, 11 Apr 2014 20:45:08 +0200 [thread overview]
Message-ID: <1397241908.4643.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6WpApJ7dn7GNYM0K7B6dyLeQVM+PRn1Ly=KXfy_96GSVA@mail.gmail.com> (sfid-20140411_202409_632105_7926309A)
On Fri, 2014-04-11 at 11:23 -0700, Luis R. Rodriguez wrote:
> compat-drivers is ancient as well, the new project is backports and we
> will be deprecating older kernels to help us scale better.
I know I pushed for the 2.6.24 deprecation, but do you see any
particular issue with other kernels < 3.0? The 2.6.24 was big and ugly,
but none of the other ones seem particularly big/ugly, and there aren't
a ton of patches either ...
Now, I'm all for dropping support if it really makes a difference, and
we might want to drop them from the ckmake tests to reduce the pain, but
I'm not entirely sure we should wholesale remove things if there are
still users for them out there.
johannes
next prev parent reply other threads:[~2014-04-11 18:45 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
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 [this message]
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=1397241908.4643.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=harrisonl@tme-inc.com \
--cc=mcgrof@frijolero.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.