From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f44.google.com ([209.85.220.44]:36755 "EHLO mail-pa0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753550AbbIMTMG (ORCPT ); Sun, 13 Sep 2015 15:12:06 -0400 Received: by padhk3 with SMTP id hk3so121546492pad.3 for ; Sun, 13 Sep 2015 12:12:05 -0700 (PDT) Received: from localhost (c-67-166-82-188.hsd1.or.comcast.net. [67.166.82.188]) by smtp.gmail.com with ESMTPSA id we9sm11775013pab.3.2015.09.13.12.12.04 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sun, 13 Sep 2015 12:12:04 -0700 (PDT) From: tmhikaru@gmail.com Date: Sun, 13 Sep 2015 12:12:04 -0700 To: stable@vger.kernel.org Subject: Re: Status of 3.10 series Message-ID: <20150913191203.GA3284@raspberrypi> References: <20150911175737.GA27997@raspberrypi> <20150911220625.GB7888@kroah.com> <20150912054745.GB15464@1wt.eu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg" Content-Disposition: inline In-Reply-To: <20150912054745.GB15464@1wt.eu> Sender: stable-owner@vger.kernel.org List-ID: --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 12, 2015 at 07:47:45AM +0200, Willy Tarreau wrote: > On Fri, Sep 11, 2015 at 03:06:25PM -0700, Greg KH wrote: > > On Fri, Sep 11, 2015 at 10:57:37AM -0700, tmhikaru@gmail.com wrote: > > > Hi there, I'm not sure if I'm emailing the correct address to ask > > > this question, but when I tried emailing Greg KH directly, I was repl= ied to > > > by a bot saying the message had been discarded and one of its suggest= ions > > > was to email this address, which it claims is the -stable mailing lis= t. I > > > did not know that this existed before now, so please notify me if I'm= asking > > > this question in the wrong place. > >=20 > > It's the correct place. > >=20 > > > In any case, I've heard rumors about work ending this month on the > > > 3.10 -stable series, though I've seen and heard no evidence of such o= ther > > > than Greg KH's declaration in september of 2013 that he'd maintain it= for at > > > least two years. It would not be a difficult thing for me to switch = to a > > > newer kernel series if I need to, so I'd like to know wether there is= any > > > fact to this rumor or not. > >=20 > > Yes, I will be stopping 3.10 soon, and yes, you should be planning to > > move to a newer kernel right now, you should have started planning 6 > > months ago, if not earlier. What is keeping you from moving to 4.1 > > today? >=20 > Or even 3.14 if he needs something moving slower. FWIW, we're currently > in the process of switching our products from 3.10 to 3.14 and the > transition has been very smooth. >=20 > Willy Thank you for your suggestion, although 4.1.6 is working fine at the moment. If you're curious why I didn't stop trying to use 3.10.x until now, it's simply because I didn't know it was going to stop being supported soon= =2E=20 I don't remember reading any notices anywhere that gave an indication it would not be supported soon. In fact, the only thing I could find about it at all that gave me some idea of what to expect was Greg KH's initial blog in september 2013 saying he'd support it for about two years. I only found that after I'd heard rumors claiming that it was no longer going to get any updates at all, which I scoffed at since there was no notice of such in the LKML I could find, nor could I find anything saying so via google. I would have expected a notice saying that a kernel series was ending to have some kind of search result, and I'm baffled that I couldn't find anything. Obviously my understanding of the situation was incorrect, and I'd like to prevent this from happening again. Perhaps I was looking in the wrong place, is there some place that lists or estimates when the -stable kernels, including LTS ones will no longer be recieving updates? If not, what indicators should I look for on a kernel series going out of support? I'd really like to avoid having to bother your list about this sort of thing again. Thank you for the help, Timothy McGrath --gKMricLos+KVdGMg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQEVAwUBVfXKg5EncCrqzVruAQJJ2Qf/SRTjMLEaiR/nwhNenWPs1FkwbftFeTxI V6YSBF5LAZJNVitjEZx5ukvcX+haL2BVh5sJNKzc/d8IjiIKXEe/Iipdss2PhlYr tYjKG91RXhrjaPc42RMl7a2uPcbm8syHb0tLZuMsLghIP8Gj16t1H4pN3/JktTo2 PCyaOcE13rKm4gIn9KBCWQO9SkAc//ZW7HFC+5Wr5LPJQHM/V61sVIzu+E4fsZUy 8N8UCbTgRFYq8FzrUwLK1JIasNGmPK8/E8sTVzIFReCViw3MnlJ2aRFQzC2FULXW n/gvDybMQomncT4Q8JTiZ6O/bWdejm3d+grTiMo2YcSe+LY6u816OA== =lOW7 -----END PGP SIGNATURE----- --gKMricLos+KVdGMg--