From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] linux-yocto: restoring LINUX_VERSION ?= "3.0"
Date: Fri, 19 Aug 2011 10:43:00 +0100 [thread overview]
Message-ID: <1313746981.6733.268.camel@phil-desktop> (raw)
In-Reply-To: <e7036174cf607031e13323564f402c7b805e4572.1313730559.git.bruce.ashfield@windriver.com>
On Fri, 2011-08-19 at 01:20 -0400, Bruce Ashfield wrote:
> diff --git a/meta/recipes-kernel/linux/linux-yocto_3.0.bb b/meta/recipes-kernel/linux/linux-yocto_3.0.bb
> index 44f1ebe..5d9871f 100644
> --- a/meta/recipes-kernel/linux/linux-yocto_3.0.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto_3.0.bb
> @@ -11,7 +11,7 @@ KMACHINE_qemuarm = "yocto/standard/arm-versatile-926ejs"
> KBRANCH = ${KMACHINE}
> KMETA = meta
>
> -LINUX_VERSION ?= "3.0.1"
> +LINUX_VERSION ?= "3.0"
> LINUX_VERSION_EXTENSION ?= "-yocto-${LINUX_KERNEL_TYPE}"
>
> SRCREV_machine_qemuarm = "36b4cdddcafc711f0ec9ad97882f23a6443c61b2"
That's going to cause PV to go backwards, right? If you're going to do
that then you probably ought to consider bumping PE to retain
monotonicity.
p.
next prev parent reply other threads:[~2011-08-19 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 5:20 [PATCH 0/3] linux-yocto: consolidated pull request Bruce Ashfield
2011-08-19 5:20 ` [PATCH 1/3] linux-yocto: restoring LINUX_VERSION ?= "3.0" Bruce Ashfield
2011-08-19 9:43 ` Phil Blundell [this message]
2011-08-19 12:53 ` Bruce Ashfield
2011-08-19 17:24 ` Richard Purdie
2011-08-19 19:05 ` Khem Raj
2011-08-19 20:51 ` Bruce Ashfield
2011-08-20 3:51 ` Bruce Ashfield
2011-08-19 5:20 ` [PATCH 2/3] linux-yocto: move more default values into linux-yocto.inc Bruce Ashfield
2011-08-19 5:20 ` [PATCH 3/3] linux-yocto: update SRCREVs for 3.0.3 Bruce Ashfield
2011-08-20 5:08 ` [PATCH 0/3] linux-yocto: consolidated pull request Bruce Ashfield
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=1313746981.6733.268.camel@phil-desktop \
--to=philb@gnu.org \
--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