From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [RFC] EOL of kernels < 3.2 and removal of support in batman-adv
Date: Tue, 01 Mar 2016 17:54:43 +0100 [thread overview]
Message-ID: <2589855.Wxd0lgVuKV@bentobox> (raw)
[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]
Hi,
the oldest kernel still supported via linux-stable reached its EOL [1]. It
looks like also the distribution releases with such an old kernel are starting
to die [2]. So I would propose to first disable the checks for kernels < 3.2
from the daily build_tests [3]. Then someone would have to change the oldest
supported kernel in README.external and CHANGELOG. The last step would be to
remove the actual support from the compat files [4,5].
This would remove 13 of the ~38 supported kernels. Or to say it with years:
The oldest kernel supported will only be 4 years old and not anymore ~7 years.
Any opinions about that?
Kind regards,
Sven
[1] https://lkml.org/lkml/2016/1/29/647
[2] Debian squeeze LTS ended on 2016-02-29
https://wiki.debian.org/LTS/Using
[3] https://patchwork.open-mesh.org/patch/4588/
[4] https://patchwork.open-mesh.org/patch/4592/
[5] Yes, this should remove the really fantastic warning
"subtraction of functions? Share your drugs"
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-03-01 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 16:54 Sven Eckelmann [this message]
2016-03-01 19:18 ` [B.A.T.M.A.N.] [RFC] EOL of kernels < 3.2 and removal of support in batman-adv Antonio Quartulli
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=2589855.Wxd0lgVuKV@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.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