From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [PATCH] [poky-extras] linux-yocto*3.8: Add bbappend for linux-yocto 3.8 recipes
Date: Wed, 3 Apr 2013 20:58:27 -0400 [thread overview]
Message-ID: <515CD033.2000807@windriver.com> (raw)
In-Reply-To: <9df95d49188bacbe180bfac67edfaa682d542ed3.1365027385.git.dvhart@linux.intel.com>
On 13-04-03 6:16 PM, Darren Hart wrote:
> Enable meta-kernel-dev support for the 3.8 kernels.
Acked-by: Bruce Ashfield <bruce.ashfield@windriver.com>
I have something similar local to my machine that I hadn't gotten
around to pushing out.
Cheers,
Bruce
>
> Signed-off-by: Darren Hart<dvhart@linux.intel.com>
> ---
> .../linux/linux-yocto-rt_3.8.bbappend | 25 ++++++++++++++++++++
> .../recipes-kernel/linux/linux-yocto_3.8.bbappend | 25 ++++++++++++++++++++
> 2 files changed, 50 insertions(+), 0 deletions(-)
> create mode 100644 meta-kernel-dev/recipes-kernel/linux/linux-yocto-rt_3.8.bbappend
> create mode 100644 meta-kernel-dev/recipes-kernel/linux/linux-yocto_3.8.bbappend
>
> diff --git a/meta-kernel-dev/recipes-kernel/linux/linux-yocto-rt_3.8.bbappend b/meta-kernel-dev/recipes-kernel/linux/linux-yocto-rt_3.8.bbappend
> new file mode 100644
> index 0000000..18eab0d
> --- /dev/null
> +++ b/meta-kernel-dev/recipes-kernel/linux/linux-yocto-rt_3.8.bbappend
> @@ -0,0 +1,25 @@
> +FILESEXTRAPATHS := "${THISDIR}/${PN}"
> +
> +COMPATIBLE_MACHINE = "${MACHINE}"
> +
> +# Note: put these in your local.conf to avoid multi-kernel build errors
> +# PREFERRED_VERSION_linux-yocto-rt_${MACHINE} = "3.8%"
> +
> +# KMACHINE is the branch to build
> +# KMACHINE_<MACHINE> ?= "yocto/${LINUX_KERNEL_TYPE}/${KMACHINE}"
> +
> +# KERNEL_FEATURES are features to be added to the kernel, and must
> +# point to configurations stored on the 'meta' branch of the kernel
> +# that is being built.
> +# KERNEL_FEATURES ?=<FOO>
> +
> +# It is often nice to have a local clone of the kernel repos, to
> +# allow patches to be staged, branches created, etc. Modify
> +
> +# KSRC_linux_yocto_3_8 to point to your local clone as appropriate.
> +# KSRC_linux_yocto_3_8 ?= "/path/to/local/linux-yocto-3.8.git/"
> +#SRC_URI = "git://${KSRC_linux_yocto_3_8};protocol=file;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
> +
> +SRCREV_machine_${MACHINE}="${AUTOREV}"
> +SRCREV_meta="${AUTOREV}"
> +LOCALCOUNT = "0"
> diff --git a/meta-kernel-dev/recipes-kernel/linux/linux-yocto_3.8.bbappend b/meta-kernel-dev/recipes-kernel/linux/linux-yocto_3.8.bbappend
> new file mode 100644
> index 0000000..9e61e33
> --- /dev/null
> +++ b/meta-kernel-dev/recipes-kernel/linux/linux-yocto_3.8.bbappend
> @@ -0,0 +1,25 @@
> +FILESEXTRAPATHS := "${THISDIR}/${PN}"
> +
> +COMPATIBLE_MACHINE = "${MACHINE}"
> +
> +# Note: put these in your local.conf to avoid multi-kernel build errors
> +# PREFERRED_VERSION_linux-yocto_${MACHINE} = "3.8%"
> +
> +# KMACHINE is the branch to build
> +# KMACHINE_<MACHINE> ?= "yocto/${LINUX_KERNEL_TYPE}/${KMACHINE}"
> +
> +# KERNEL_FEATURES are features to be added to the kernel, and must
> +# point to configurations stored on the 'meta' branch of the kernel
> +# that is being built.
> +# KERNEL_FEATURES ?=<FOO>
> +
> +# It is often nice to have a local clone of the kernel repos, to
> +# allow patches to be staged, branches created, etc. Modify
> +
> +# KSRC_linux_yocto_3_8 to point to your local clone as appropriate.
> +# KSRC_linux_yocto_3_8 ?= "/path/to/local/linux-yocto-3.8.git/"
> +# SRC_URI = "git://${KSRC_linux_yocto_3_8};protocol=file;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta"
> +
> +SRCREV_machine_${MACHINE}="${AUTOREV}"
> +SRCREV_meta="${AUTOREV}"
> +LOCALCOUNT = "0"
prev parent reply other threads:[~2013-04-04 0:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 22:16 [PATCH] [poky-extras] linux-yocto*3.8: Add bbappend for linux-yocto 3.8 recipes Darren Hart
2013-04-04 0:58 ` Bruce Ashfield [this message]
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=515CD033.2000807@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.