From: Jani Nikula <jani.nikula@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: ksummit <ksummit-discuss@lists.linuxfoundation.org>,
Dave Airlie <airlied@linux.ie>,
David Miller <davem@davemloft.net>,
Doug Ledford <dledford@redhat.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [Ksummit-discuss] "Maintainer summit" invitation discussion
Date: Thu, 20 Apr 2017 15:22:26 +0300 [thread overview]
Message-ID: <87fuh3s1z1.fsf@intel.com> (raw)
In-Reply-To: <20170420105933.GA26134@kroah.com>
On Thu, 20 Apr 2017, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> On Thu, Apr 20, 2017 at 11:17:18AM +0300, Jani Nikula wrote:
>> On Wed, 19 Apr 2017, Linus Torvalds <torvalds@linux-foundation.org> wrote:
>> > Yeah, I don't think we can do much about distros that intentionally
>> > want to stay behind and backport.
>>
>> /me looks at https://www.kernel.org/
>>
>> 1 stable, 8 longterm, and 1 eol'd longterm kernels. The oldest longterm
>> is based on a five years old release.
>
> That 5 year old kernel is due to Debian's looney release schedule, go
> take it up with them :)
>
>> I just think the multitude of longterm kernels are sending a message
>> that it's perfectly fine to stay behind. Don't get me wrong, I know why
>> they are there, but I still think in the past the focus on encouraging
>> to always use the latest stable kernel was stronger.
>
> And how do you suggest that we do that any more than we currently do?
> (i.e. I go around and talk to companies all the time about this issue,
> did a tour of Asia last month, and will be talking to some US-based
> companies next month.)
>
> As you say, you know why they are there, so why is that not a valid
> reason in itself? :)
Well, I'm just saying it's a double edged sword. Accommodating the
longterms says it's okay to rely on them, but then you go around the
world telling people they shouldn't do that anyway. It's a tradeoff.
Or maybe you just like traveling? ;)
> And you will note (although everyone seems to ignore it), that we are
> now only adding 1 new LTS kernel a year, and have been for the past few
> years, in order to cut down on the proliferation we had 3-4 years back.
I think that's a step in the right direction. How about having a shorter
lifetime too, despite "longterm"? Of course that would conflict with
what the distros are doing, and this may not be a popular view, but I'm
wondering if it's overall a net positive to give an appearance of
kernel.org endorsing all these ancient kernels?
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2017-04-20 12:22 UTC|newest]
Thread overview: 135+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 18:59 Linus Torvalds
2017-04-18 19:50 ` Takashi Iwai
2017-04-18 20:13 ` Linus Torvalds
2017-04-18 20:21 ` Jiri Kosina
2017-04-18 20:36 ` Takashi Iwai
2017-04-18 20:29 ` Takashi Iwai
2017-04-18 20:33 ` Laura Abbott
2017-04-18 21:15 ` Mauro Carvalho Chehab
2017-04-19 22:36 ` Jonathan Corbet
2017-04-19 22:41 ` Jiri Kosina
2017-04-19 23:36 ` Josh Triplett
2017-04-19 23:51 ` Jiri Kosina
2017-04-20 1:04 ` Josh Triplett
2017-04-20 7:38 ` Jani Nikula
2017-04-20 5:23 ` Christoph Hellwig
2017-04-20 13:33 ` James Bottomley
2017-04-20 14:40 ` Alexey Dobriyan
2017-04-20 14:52 ` Ingo Molnar
2017-04-20 14:47 ` Jonathan Corbet
2017-04-20 15:34 ` James Bottomley
2017-04-20 11:25 ` Mauro Carvalho Chehab
2017-04-19 15:37 ` Doug Ledford
2017-04-19 16:18 ` Linus Torvalds
2017-04-19 16:24 ` Doug Ledford
2017-04-19 18:11 ` Justin Forbes
2017-04-19 21:52 ` Geert Uytterhoeven
2017-04-19 18:21 ` Laura Abbott
2017-04-20 8:31 ` Jani Nikula
2017-04-20 12:35 ` Mark Brown
2017-04-20 13:01 ` Jani Nikula
2017-04-21 8:41 ` Alexandre Belloni
2017-04-21 14:46 ` David Miller
2017-04-20 8:17 ` Jani Nikula
2017-04-20 10:59 ` Greg Kroah-Hartman
2017-04-20 12:22 ` Jani Nikula [this message]
2017-04-20 13:03 ` Greg Kroah-Hartman
2017-04-20 14:49 ` Mark Brown
2017-04-19 19:25 ` Laurent Pinchart
2017-04-19 19:40 ` Linus Torvalds
2017-04-19 19:45 ` Jens Axboe
2017-04-19 19:50 ` Laurent Pinchart
2017-04-19 19:55 ` James Bottomley
2017-04-20 8:26 ` Daniel Vetter
2017-04-20 13:25 ` James Bottomley
2017-04-25 16:02 ` Bart Van Assche
2017-04-25 16:38 ` Guenter Roeck
2017-04-25 16:56 ` Mark Brown
2017-04-26 3:47 ` Bart Van Assche
2017-04-26 8:39 ` Geert Uytterhoeven
2017-04-26 14:21 ` Mark Brown
2017-04-26 14:51 ` David Miller
2017-04-26 15:15 ` Mark Brown
2017-04-26 8:42 ` Dan Carpenter
2017-04-26 13:58 ` Martin K. Petersen
2017-04-26 14:15 ` Andrew Lunn
2017-04-26 15:42 ` Martin K. Petersen
2017-04-26 14:31 ` James Bottomley
2017-04-26 14:34 ` Jiri Kosina
2017-04-26 14:43 ` James Bottomley
2017-04-27 9:06 ` Jani Nikula
2017-04-27 10:41 ` Lee Jones
2017-04-27 11:02 ` Hannes Reinecke
2017-04-27 14:17 ` James Bottomley
2017-04-28 0:24 ` Rafael J. Wysocki
2017-04-27 15:40 ` Wolfram Sang
2017-04-26 15:02 ` Bart Van Assche
2017-04-26 15:25 ` James Bottomley
2017-04-26 15:36 ` Mark Brown
2017-04-19 20:14 ` Josh Triplett
2017-04-19 21:30 ` Laurent Pinchart
2017-04-20 5:44 ` Julia Lawall
2017-04-20 8:54 ` Laurent Pinchart
2017-04-19 19:58 ` Konstantin Ryabitsev
2017-04-19 20:20 ` Jiri Kosina
2017-04-18 20:00 ` Dave Airlie
2017-04-18 20:29 ` Laurent Pinchart
2017-04-18 20:38 ` Daniel Vetter
2017-04-18 20:56 ` Linus Torvalds
2017-04-18 21:39 ` Daniel Vetter
2017-04-20 19:02 ` Mark Brown
2017-04-18 20:06 ` Serge E. Hallyn
2017-04-18 20:11 ` Greg Kroah-Hartman
2017-04-18 20:21 ` Linus Torvalds
2017-04-25 15:09 ` Chris Mason
2017-04-19 0:22 ` Stephen Rothwell
2017-04-19 13:35 ` Shuah Khan
2017-04-19 20:20 ` James Bottomley
2017-04-19 20:27 ` Jiri Kosina
2017-04-20 10:24 ` Mauro Carvalho Chehab
2017-04-21 8:51 ` Alexandre Belloni
2017-04-21 8:55 ` Julia Lawall
2017-04-21 8:59 ` Wolfram Sang
2017-04-21 14:45 ` Mauro Carvalho Chehab
2017-04-21 10:34 ` Michael Ellerman
2017-04-21 15:06 ` Mauro Carvalho Chehab
2017-04-21 23:37 ` James Bottomley
2017-04-20 16:01 ` Dan Williams
2017-04-21 11:07 ` Michael Ellerman
2017-04-21 17:06 ` Mauro Carvalho Chehab
2017-04-21 23:19 ` Bjorn Helgaas
2017-04-19 20:26 ` Arnd Bergmann
2017-04-20 8:53 ` Daniel Vetter
2017-04-20 11:30 ` Arnd Bergmann
2017-04-20 13:46 ` Daniel Vetter
2017-04-24 14:02 ` Olof Johansson
2017-04-24 16:17 ` Linus Walleij
2017-04-24 17:29 ` Olof Johansson
2017-04-24 17:58 ` Mark Brown
2017-04-25 9:10 ` Lee Jones
2017-04-29 21:00 ` Daniel Vetter
2017-04-29 21:39 ` James Bottomley
2017-04-30 12:45 ` Mark Brown
2017-04-30 19:12 ` Olof Johansson
2017-05-02 8:09 ` Lee Jones
2017-04-20 19:26 ` Mark Brown
2017-04-21 11:03 ` Alexandre Belloni
2017-04-24 13:14 ` Nicolas Ferre
2017-04-19 21:05 ` Andy Lutomirski
2017-04-19 21:32 ` Linus Torvalds
2017-05-23 17:58 ` Linus Torvalds
2017-05-23 18:17 ` Randy Dunlap
2017-05-23 18:47 ` Thomas Gleixner
2017-05-23 20:34 ` Linus Torvalds
2017-05-23 19:29 ` James Bottomley
2017-05-24 3:34 ` David Miller
2017-05-24 4:55 ` Linus Torvalds
2017-04-21 0:35 ` Rafael J. Wysocki
2017-09-20 14:45 ` Doug Ledford
2017-09-20 15:07 ` James Bottomley
2017-09-20 15:22 ` Doug Ledford
2017-09-20 15:31 ` James Bottomley
2017-09-20 15:58 ` Doug Ledford
2017-09-20 22:55 ` Theodore Ts'o
2017-09-21 9:33 ` Leon Romanovsky
2017-09-21 4:54 ` James Morris
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=87fuh3s1z1.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@linux.ie \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox