All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jeremiah 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, 23 Aug 2011 21:46:36 -0700	[thread overview]
Message-ID: <20110824044636.GC786@kroah.com> (raw)
In-Reply-To: <056B8993-8B70-470A-AFDD-53F587AF3312@jeremiahfoster.com>

On Wed, Aug 17, 2011 at 12:33:56PM +0200, Jeremiah Foster wrote:
> 
> On Aug 17, 2011, at 00:33, Greg KH wrote:
> > 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?  
> 
> My understanding is yes. It appears to be a business opportunity for
> many OSVs and others as well, but the distro's are doing a good job so
> increasingly commercial companies are turning to distros, at least
> initially.
> 
> > Are they
> > somehow not doing this job well?  
> 
> I think they are doing the job well which is why there is increasing
> choice; use a distro or pay for an OSV? Rely on the community or
> develop in-house competence? These questions are new, at least for the
> automotive industry, since previously it was all proprietary all the
> time.

Yes, it's a new model that they need to get used to :)

> > Do they need help from the community
> > instead to help define, implement, and maintain this for them?
> 
> I think the answer is yes.
> 
> > 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 it helps at all, I can bring up this topic inside GENIVI and ask if
> there are OEMs, Tier 1s and others who would be interested in how to
> identify a kernel that is appropriate for their long-term needs. I
> have participated in GENIVI discussions like this previously and there
> has not necessarily been clarity. Having your perspective and the
> perspective of others with experience in kernel maintenance would be
> helpful.

Please do.  My view of GENIVI from the outside is that it reminds me a
lot of the problems that plagued the old CGL initiative.  Hopefully that
is incorrect on my part.

If there's anyone, or any group, I should be talking to about this, or
any meeting I could attend to help explain it all better, please let me
know, I am more than willing to do so.

> > 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?  
> 
> That is the eternal question. For the auto industry it often boils
> down to the cost / benefit ratio and the cost sensitivity for
> production vehicles per unit is a major factor in what they choose. I
> think if they can find a reasonable long-term kernel they'll help
> maintain it in conjunction with the community.

That's good to hear, any help is appreciated.

Mostly I want to know what patches should be applied, that fix problems
they have.  That and testing the -rc releases would be wonderful.

> > If the latter,
> > I'd be very happy to work with them, contacts are greatly appreciated.
> 
> Very generous of you. Let me see if I can pull together a list of
> people where this can be discussed.

That would be great, odds are, a new thread can be started, and everyone
on cc: taken off, as I doubt they care about this :)

thanks,

greg k-h

  parent reply	other threads:[~2011-08-24  4:48 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     ` [stable] " Greg KH
2011-08-17 10:33       ` Jeremiah Foster
2011-08-17 20:20         ` david
2011-08-24  4:47           ` Greg KH
2011-08-24  4:46         ` Greg KH [this message]
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=20110824044636.GC786@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.