From: Solomon Peachy <pizza@shaftnet.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@frijolero.org>,
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 15:26:19 -0400 [thread overview]
Message-ID: <20140411192619.GA16958@shaftnet.org> (raw)
In-Reply-To: <1397241908.4643.1.camel@jlt4.sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 1331 bytes --]
On Fri, Apr 11, 2014 at 08:45:08PM +0200, Johannes Berg wrote:
> 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.
Speaking as an end-user of compat-wireless, compat-drivers, and later
backports, I used them because I was stuck using a nominally-outdated,
heavily-patched vendor-supplied kernel for an SoC/board that wasn't
[well] supported by the mainline kernel.
To make things worse, I was trying to get a driver for the cw1200 family
mainlined. It finally made it into 3.11, but at the time, the bills
were being paid by supporting clients that were stuck on 2.6.28, 2.6.35
and 3.0, which coincidentally were what I was using to develop/test the
driver at the time of the 3.11 release.
I no longer have any skin in the game (I've moved on to mostly
microcontroller work) but please, don't drop support for older kernels
if the only reason is to save release-time checks, or worse, "just
because"
My $0.02,
- Solomon
--
Solomon Peachy pizza at shaftnet dot org
Delray Beach, FL ^^ (email/xmpp) ^^
Quidquid latine dictum sit, altum viditur.
[-- Attachment #2: Type: application/pgp-signature, Size: 155 bytes --]
next prev parent reply other threads:[~2014-04-11 20:06 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
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 [this message]
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=20140411192619.GA16958@shaftnet.org \
--to=pizza@shaftnet.org \
--cc=backports@vger.kernel.org \
--cc=harrisonl@tme-inc.com \
--cc=johannes@sipsolutions.net \
--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.