Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: celston@katalix.com,
	"Patches and discussions about the oe-core layer"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] bitbake.conf: update OLDEST_KERNEL to 2.6.0
Date: Fri, 8 Jul 2011 10:49:13 +0100	[thread overview]
Message-ID: <201107081049.13142.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <1310114794.3629.7.camel@ce-laptop>

On Friday 08 July 2011 09:46:34 Chris Elston wrote:
> It's very rare that we get a free hand in the choice of kernel version.
> We get stuck with whichever version the silicon vendor chooses to
> support, so it would be bad for us if we couldn't use an older kernel in
> our layers.

Just out of interest, what's the oldest kernel you have to deal with in your 
current/recent projects?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2011-07-08  9:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-07 13:11 [PATCH 0/2] update OLDEST_KERNEL Paul Eggleton
2011-07-07 13:11 ` [PATCH 1/2] bitbake.conf: update OLDEST_KERNEL to 2.6.0 Paul Eggleton
2011-07-07 14:24   ` Koen Kooi
2011-07-07 14:34     ` Paul Eggleton
2011-07-07 23:15       ` Richard Purdie
2011-07-08  5:21       ` Khem Raj
2011-07-08  8:38         ` Paul Eggleton
2011-07-08  8:46           ` Chris Elston
2011-07-08  9:49             ` Paul Eggleton [this message]
2011-07-08  9:53           ` Phil Blundell
2011-07-08 10:03             ` Paul Eggleton
2011-07-08 10:12               ` Phil Blundell
2011-07-08 10:20                 ` Paul Eggleton
2011-07-08 14:17           ` Khem Raj
2011-07-08 16:28             ` Richard Purdie
2011-07-07 13:11 ` [PATCH 2/2] eglibc: bump PR for OLDEST_KERNEL change Paul Eggleton

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=201107081049.13142.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=celston@katalix.com \
    --cc=openembedded-core@lists.openembedded.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