From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [PATCH 1/1] linux-yocto-tiny: Bump SRCREV and PV to 3.0.18
Date: Mon, 27 Feb 2012 00:08:24 -0500 [thread overview]
Message-ID: <4F4B0FC8.7030807@windriver.com> (raw)
In-Reply-To: <e43a5b93817dc1a4ed2c526e3e9ea825347bf212.1330319008.git.dvhart@linux.intel.com>
On 12-02-27 12:04 AM, Darren Hart wrote:
> Bring linux-yocto-tiny inline with the other 3.0 linux-yocto-* recipes.
> Built and booted for qemux86.
I'm just about to pull the trigger (i.e. a matter of hours) on 3.0.22. If
you want to wait for that, or let this stand, either is fine with me, but
I thought I'd warn :)
Cheers,
Bruce
>
> Signed-off-by: Darren Hart<dvhart@linux.intel.com>
> ---
> meta/recipes-kernel/linux/linux-yocto-tiny_3.0.bb | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.0.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.0.bb
> index 061476c..fe4033b 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-tiny_3.0.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.0.bb
> @@ -5,10 +5,10 @@ require recipes-kernel/linux/linux-yocto.inc
> KMACHINE = "yocto/standard/base"
> KBRANCH = "${KMACHINE}"
>
> -LINUX_VERSION ?= "3.0.12"
> +LINUX_VERSION ?= "3.0.18"
>
> -SRCREV_machine ?= "f389d310965a56091f688b28ea8be6d9cbb7fbbe"
> -SRCREV_meta ?= "04a52a32cbdf0972033b97b83eaa83eb275dfdc9"
> +SRCREV_machine ?= "5df0b4c2538399aed543133b3855f809adf08ab8"
> +SRCREV_meta ?= "b78a519841bd8b477cad599af8d38df6760445c1"
>
> PR = "r1"
> PV = "${LINUX_VERSION}+git${SRCPV}"
next prev parent reply other threads:[~2012-02-27 5:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 5:04 [PATCH 0/1] linux-yocto-tiny: Bump SRCREV and PV to 3.0.18 Darren Hart
2012-02-27 5:04 ` [PATCH 1/1] " Darren Hart
2012-02-27 5:08 ` Bruce Ashfield [this message]
2012-02-27 5:13 ` Darren Hart
2012-02-27 5:18 ` 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=4F4B0FC8.7030807@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=yocto@yoctoproject.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.