From: Luca Coelho <luca@coelho.fi>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>,
Johannes Berg <johannes@sipsolutions.net>,
backports@vger.kernel.org
Subject: Re: deprecating more kernel versions
Date: Tue, 07 Feb 2017 06:20:23 +0200 [thread overview]
Message-ID: <1486441223.3070.2.camel@coelho.fi> (raw)
In-Reply-To: <04ef169d-49b1-98e0-1db6-7c4e7e9b5c9f@broadcom.com>
On Mon, 2017-02-06 at 23:45 +0100, Arend Van Spriel wrote:
> On 6-2-2017 17:37, Johannes Berg wrote:
> > What kernel versions do you still need?
> >
> > For example, 3.0 is getting really quite old, the oldest long-term
> > stable is 3.2.x now.
>
> We currently backport internal tree and wireless-testing nightly to 3.10
> and 3.11 kernels.
I think capping at 3.10 is reasonable. Internally, we have been
supporting 3.8+, but we got permission to support only 3.12 and above.
Last time we nuked support for older kernels [1], we were supporting
only 15 kernel versions (3.0 through 3.14). Now we are at 30 (3.0
through 4.10 -- sort of). If we make the cut at 3.10 we are at 20,
which is still a lot more conservative than our last "nuke".
[1] https://git.kernel.org/cgit/linux/kernel/git/backports/backports.git/commit/?id=be4a0f9ad7e17670d7a30c9e94d5dd918425f90a
--
Cheers,
Luca.
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2017-02-07 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 16:37 deprecating more kernel versions Johannes Berg
2017-02-06 22:45 ` Arend Van Spriel
2017-02-07 4:20 ` Luca Coelho [this message]
2017-02-07 4:48 ` Steve deRosier
2017-02-07 6:38 ` Johannes Berg
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=1486441223.3070.2.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=arend.vanspriel@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=johannes@sipsolutions.net \
/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.