From: Chris Elston <celston@katalix.com>
To: 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, 08 Jul 2011 09:46:34 +0100 [thread overview]
Message-ID: <1310114794.3629.7.camel@ce-laptop> (raw)
In-Reply-To: <201107080938.37370.paul.eggleton@linux.intel.com>
On Fri, 2011-07-08 at 09:38 +0100, Paul Eggleton wrote:
> On Friday 08 July 2011 06:21:16 Khem Raj wrote:
> > If oe-core never supported older kernel than 2.6.37 then setting it to
> > 2.6.37 would be better IMO
>
> It's not necessarily just about oe-core - it's about what layers get used on
> top, and some of those will be using kernels older than 2.6.37.
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.
Cheers,
Chris.
next prev parent reply other threads:[~2011-07-08 9:45 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 [this message]
2011-07-08 9:49 ` Paul Eggleton
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=1310114794.3629.7.camel@ce-laptop \
--to=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