All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Jeremiah C. Foster" <jeremiah@jeremiahfoster.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
	linux-kernel@vger.kernel.org, stable@kernel.org,
	akpm@linux-foundation.org, torvalds@linux-foundation.org,
	stable-review@kernel.org, alan@lxorguk.ukuu.org.uk,
	Debian kernel maintainers <debian-kernel@lists.debian.org>
Subject: Re: [stable] [Stable-review] Future of the -longterm kernel releases (i.e. how we pick them).
Date: Tue, 16 Aug 2011 15:33:27 -0700	[thread overview]
Message-ID: <20110816223327.GA1534@kroah.com> (raw)
In-Reply-To: <17669FB8-C6FF-4B1F-9765-F1FD991D14CB@jeremiahfoster.com>

On Tue, Aug 16, 2011 at 09:26:24PM +0200, Jeremiah C. Foster wrote:
> I'd like to echo Ben's sentiment, particularly in the area of automotive. 
> A car has to be supported with parts for at least ten years, often longer, 
> and this includes the build system for the infotainment software.
> The GENIVI Alliance is now building infotainment systems for their member 
> companies (BMW, GM, PSA, Hyundai, etc.) which will have to preserve a 
> working kernel for a long time, like lark's tongues in aspic. So there is an 
> interest in a "longterm, stable" kernel in the automotive industry. Furthermore,
> know-how around choosing a long term kernel relevant to a car is in short 
> supply, so there is a lot of reliance on the distros and commercial OSVs in 
> this regard.

Isn't that the job of the distros and commercial OSVs today?  Are they
somehow not doing this job well?  Do they need help from the community
instead to help define, implement, and maintain this for them?

I'm genuinely curious about this, I haven't heard this directly from
users before, only from companies who are in this line of work, wanting
help in doing this for them, for a variety of odd reasons.

If so, doesn't this imply that maybe those users should be choosing a
different company for this support, or that they have given up on this
and want to work directly with the community instead?  If the latter,
I'd be very happy to work with them, contacts are greatly appreciated.

greg k-h

  reply	other threads:[~2011-08-16 22:34 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-15  4:15 Future of the -longterm kernel releases (i.e. how we pick them) Greg KH
2011-08-15  6:48 ` Jörg-Volker Peetz
2011-08-15  7:06   ` david
2011-08-15  7:16     ` Teck Choon Giam
2011-08-15  7:25       ` david
2011-08-15  7:38         ` Teck Choon Giam
2011-08-15  7:57         ` Jörg-Volker Peetz
2011-08-17 11:07       ` James Courtier-Dutton
2011-08-15  7:19   ` Jörg-Volker Peetz
2011-08-15  7:21 ` david
2011-08-15 14:21   ` Greg KH
2011-08-16  2:26     ` [Stable-review] " Ben Hutchings
2011-08-16  2:56       ` [stable] " Greg KH
2011-08-16  3:31         ` Ben Hutchings
2011-08-16  5:26     ` Daniel Taylor
2011-08-24 23:57       ` Greg KH
2011-08-15  7:33 ` [Stable-review] " Willy Tarreau
2011-08-15 14:18   ` [stable] " Greg KH
2011-08-15 15:04 ` [stable] " Tim Gardner
2011-08-16  2:09 ` [Stable-review] " Ben Hutchings
2011-08-16  2:57   ` [stable] " Greg KH
2011-08-16 19:26   ` Jeremiah C. Foster
2011-08-16 22:33     ` Greg KH [this message]
2011-08-17 10:33       ` [stable] " Jeremiah Foster
2011-08-17 20:20         ` david
2011-08-24  4:47           ` Greg KH
2011-08-24  4:46         ` Greg KH
2011-08-24 13:03           ` Jeremiah Foster
2011-08-16 23:01 ` Tim Bird
2011-08-17  4:58   ` Greg KH
2011-08-17 13:21     ` Mark Brown
2011-08-17 17:33       ` Brian Swetland
2011-08-24  4:57         ` Greg KH
2011-08-25  4:49           ` Brian Swetland
2011-08-26  0:03             ` Greg KH
2011-08-18  0:33     ` [Stable-review] " Ben Hutchings
2011-08-18 11:28       ` Pasi Kärkkäinen

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=20110816223327.GA1534@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ben@decadent.org.uk \
    --cc=debian-kernel@lists.debian.org \
    --cc=jeremiah@jeremiahfoster.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable-review@kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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.