All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Anton Altaparmakov <anton@tuxera.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Merging backported fscrypt to 4.4?
Date: Fri, 13 Oct 2017 16:57:50 +0200	[thread overview]
Message-ID: <20171013145750.GE2447@1wt.eu> (raw)
In-Reply-To: <785813EC-834E-4566-BE88-1ED966728714@tuxera.com>

Hi Anton,

On Fri, Oct 13, 2017 at 08:57:28AM +0000, Anton Altaparmakov wrote:
> Hi Willy,
> 
> > On 12 Oct 2017, at 18:26, Willy Tarreau <w@1wt.eu> wrote:
> > On Thu, Oct 12, 2017 at 01:26:26PM +0000, Anton Altaparmakov wrote:
> >>>>> You should convince your customers to use a more modern kernel :)
> >>>> 
> >>>> In fact one of our customers were moving to a more recent kernel and
> >>>> cancelled the move when the announcement about the longer 4.4 kernel
> >>>> life time was made!!!
> >>> 
> >>> Um, that's not really very wise.  You should council them about that...
> > 
> > In fact given that 4.9 will be maintained for a long time as well, there
> > is no really valid excuse for rolling back to 4.4.
> 
> Interesting.  https://www.kernel.org/category/releases.html still states 4.4
> has projected EOL 2022 whilst 4.9 is 2019 so I can see why companies are
> looking and it and jumping onto 4.4...

Well, debian 9 settled on 4.9 and will be maintained till 2022 as well :

     https://wiki.debian.org/LTS

Based on the good work done on the previous kernels, we can expect to
have a very good kernel till that date as well. Sadly there's less
communication about this but you can probably use this to reassure your
customers that it's stupid to roll back to 4.4 to reach the same EOL as
4.9 with less features and/or riskier backports.

Just my two cents. At least our appliances are now shipping on 4.9 ;-)

Willy

      reply	other threads:[~2017-10-13 14:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12 11:59 Merging backported fscrypt to 4.4? Anton Altaparmakov
2017-10-12 12:11 ` Greg KH
2017-10-12 12:30   ` Anton Altaparmakov
2017-10-12 12:49     ` Greg KH
2017-10-12 13:26       ` Anton Altaparmakov
2017-10-12 13:45         ` Greg KH
2017-10-12 13:53           ` Anton Altaparmakov
2017-10-12 17:26         ` Willy Tarreau
2017-10-13  8:57           ` Anton Altaparmakov
2017-10-13 14:57             ` Willy Tarreau [this message]

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=20171013145750.GE2447@1wt.eu \
    --to=w@1wt.eu \
    --cc=anton@tuxera.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.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.