From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [195.159.176.226] ([195.159.176.226]:38596 "EHLO blaine.gmane.org" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1750841AbeASKjF (ORCPT ); Fri, 19 Jan 2018 05:39:05 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1ecU2Q-0005DK-8M for stable@vger.kernel.org; Fri, 19 Jan 2018 11:36:46 +0100 To: stable@vger.kernel.org From: Francesco Del Degan Subject: Re: KPTI for 4.1 LTS Date: Fri, 19 Jan 2018 10:36:29 +0000 (UTC) Message-ID: References: <20180118094017.GA28652@kroah.com> <20180119085838.GA31700@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org List-ID: On Fri, 19 Jan 2018 09:58:38 +0100, Greg KH wrote: > Really? What are you going to do when this goes end-of-life in 3 > months? Seems like you should already be planning for that, right? In EOL, we will be just like others that want to provide extended (custom) support, we are on our own. But that's is another problem, I guess. > If you will note, different people maintain the different trees, and > they all have different amounts of time they can devote to this: > https://www.kernel.org/category/releases.html I know, and my question was way more practical: Trying to avoid to start backporting work that would been trashed after few days because it was already planned or started from someone else (and not announced to ml). > If you were to provide working patches for 4.1, I'm sure that would make > things go quicker :) Sure, I will try to do it next days :-) Thanks a lot, francesco