From: Darren Hart <dvhart@linux.intel.com>
To: yocto@yoctoproject.org, bruce.ashfield@windriver.com
Subject: Re: [PATCH 02/17] meta/rt: beagleboard preempt-rt support
Date: Thu, 11 Aug 2011 01:27:14 -0700 [thread overview]
Message-ID: <4E439262.3060403@linux.intel.com> (raw)
In-Reply-To: <d3104bcb5205dffefbe8149f38f65b3edd48e03a.1313050084.git.dvhart@linux.intel.com>
On 08/11/2011 01:23 AM, Darren Hart wrote:
Oh the hypocrisy! For those of you that have caught my lack of detailed
commentary for all the added preempt-rt .scc files - you are completely
justified. I intended to paste a blurb for each and forgot by the time I
sent them out. Probably not worth resending, but I will if Bruce is a
10th as picky as I am. Apologies.
--
Darren
> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
> ---
> .../bsp/beagleboard/beagleboard-preempt-rt.scc | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
> create mode 100644 meta/cfg/kernel-cache/bsp/beagleboard/beagleboard-preempt-rt.scc
>
> diff --git a/meta/cfg/kernel-cache/bsp/beagleboard/beagleboard-preempt-rt.scc b/meta/cfg/kernel-cache/bsp/beagleboard/beagleboard-preempt-rt.scc
> new file mode 100644
> index 0000000..aa71a94
> --- /dev/null
> +++ b/meta/cfg/kernel-cache/bsp/beagleboard/beagleboard-preempt-rt.scc
> @@ -0,0 +1,7 @@
> +define KMACHINE beagleboard
> +define KTYPE preempt-rt
> +define KARCH arm
> +
> +# no new branch required, re-use the ktypes/preempt-rt branch
> +include ktypes/preempt-rt
> +include beagleboard.scc
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-08-11 8:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 8:23 [PATCH 00/17][linux-yocto-3.0:meta] preempt-rt update (3.0.1-rt8 scc's) Darren Hart
2011-08-11 8:23 ` [PATCH 01/17] meta/rt: use CONFIG_PREEMPT_RT_FULL for 3.0 kernels Darren Hart
2011-08-11 8:23 ` [PATCH 02/17] meta/rt: beagleboard preempt-rt support Darren Hart
2011-08-11 8:27 ` Darren Hart [this message]
2011-08-11 15:12 ` Bruce Ashfield
2011-08-11 8:23 ` [PATCH 03/17] meta/rt: mpc8315 " Darren Hart
2011-08-11 8:23 ` [PATCH 04/17] meta-rt: rsp " Darren Hart
2011-08-11 8:23 ` [PATCH 05/17] meta/rt: qemu-ppc32 " Darren Hart
2011-08-11 8:23 ` [PATCH 06/17] meta/rt: mti-malta32-be " Darren Hart
2011-08-11 8:23 ` [PATCH 07/17] meta/rt: arm-versatile-926ejs " Darren Hart
2011-08-11 8:23 ` [PATCH 08/17] meta/rt: crownbay " Darren Hart
2011-08-11 8:23 ` [PATCH 09/17] meta/rt: emenlow " Darren Hart
2011-08-11 8:23 ` [PATCH 10/17] meta/rt: fishriver " Darren Hart
2011-08-11 8:23 ` [PATCH 11/17] meta/rt: fri2 " Darren Hart
2011-08-11 8:23 ` [PATCH 12/17] meta/rt: jasperforest " Darren Hart
2011-08-11 8:23 ` [PATCH 13/17] meta/rt: common-pc[-64] preempt-rt no branch fix Darren Hart
2011-08-11 8:23 ` [PATCH 14/17] meta/rt: sugarbay preempt-rt support Darren Hart
2011-08-11 8:23 ` [PATCH 15/17] mpc8315e-rdb: remove boot -Os patch which is now in base Darren Hart
2011-08-11 8:23 ` [PATCH 16/17] routerstationpro: add remove-superfluous-endif patch to scc Darren Hart
2011-08-11 8:23 ` [PATCH 17/17] routerstationpro: remove CONFIG_PREEMPT* definitions Darren Hart
2011-08-11 15:11 ` [PATCH 00/17][linux-yocto-3.0:meta] preempt-rt update (3.0.1-rt8 scc's) 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=4E439262.3060403@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@windriver.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.