From: Tom Zanussi <tom.zanussi@intel.com>
To: nitin.a.kamble@intel.com
Cc: yocto@yoctoproject.org, darren.hart@intel.com
Subject: Re: [PATCH v2 5/6] jasperforest: add WEBTITLE & Compliance information
Date: Wed, 24 Oct 2012 19:34:12 -0500 [thread overview]
Message-ID: <1351125252.27553.64.camel@empanada> (raw)
In-Reply-To: <6f887e6929f52dddb5a29fd2d92c48732486febb.1351110209.git.nitin.a.kamble@intel.com>
On Wed, 2012-10-24 at 13:25 -0700, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>
> The WEBTITLE will be used to publish the BSP on the Yocto Project Website.
> And adding the Yocto Project Compliance information for the 1.3 release.
> Also specifying all the layers used from meta-intel repository.
>
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
> meta-jasperforest/README | 8 +++++++-
> meta-jasperforest/conf/machine/jasperforest.conf | 2 ++
> 2 files changed, 9 insertions(+), 1 deletions(-)
>
> diff --git a/meta-jasperforest/README b/meta-jasperforest/README
> index 12f84c2..6397ec7 100644
> --- a/meta-jasperforest/README
> +++ b/meta-jasperforest/README
> @@ -8,6 +8,12 @@ combined with the Intel 3420 PCH chipset (Ibex Peak) make up the
> 'Picket Post' CRB this BSP was developed on.
>
>
> +Compliance
> +==========
> +This BSP is compliant with Yocto Project as per requirements listed here:
> +http://www.yoctoproject.org/yocto-project-compatible-registration
> +
> +
> Dependencies
> ============
>
> @@ -21,7 +27,7 @@ This layer depends on:
> branch: master
>
> URI: git://git.yoctoproject.org/meta-intel
> - layers: intel
> + layers: meta-intel, meta-jasperforest
> branch: master
>
>
> diff --git a/meta-jasperforest/conf/machine/jasperforest.conf b/meta-jasperforest/conf/machine/jasperforest.conf
> index d661f7b..8111deb 100644
> --- a/meta-jasperforest/conf/machine/jasperforest.conf
> +++ b/meta-jasperforest/conf/machine/jasperforest.conf
> @@ -1,6 +1,8 @@
> #@TYPE: Machine
> #@NAME: jasperforest
>
> +#@WEBTITLE: Platforms with Intel Xeon C5500/C3500 series processors with Intel 3420 PCH chipset (Jasper Forest)
> +
Similarly:
Intel Xeon C5500/C3500 Series Processors with Intel 3420 PCH Chipset
(Jasper Forest)
Tom
> #@DESCRIPTION: Machine configuration for Jasper Forest Picket Post
> # systems i.e. Xeon C5500/C3500 + Intel 3420 chipset (Ibex Peak)
>
next prev parent reply other threads:[~2012-10-25 0:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 20:25 [PATCH v2 0/6] meta-intel: README updates nitin.a.kamble
2012-10-24 20:25 ` [PATCH v2 1/6] MAINTAINERS: correct pathname nitin.a.kamble
2012-10-24 20:25 ` [PATCH v2 2/6] chiefriver: add WEBTITLE & Compliance information nitin.a.kamble
2012-10-25 0:14 ` Tom Zanussi
2012-10-25 17:00 ` Kamble, Nitin A
2012-10-25 17:13 ` Kamble, Nitin A
2012-10-24 20:25 ` [PATCH v2 3/6] crownbay: " nitin.a.kamble
2012-10-25 0:30 ` Tom Zanussi
2012-10-24 20:25 ` [PATCH v2 4/6] emenlow: " nitin.a.kamble
2012-10-25 0:32 ` Tom Zanussi
2012-10-24 20:25 ` [PATCH v2 5/6] jasperforest: " nitin.a.kamble
2012-10-25 0:34 ` Tom Zanussi [this message]
2012-10-24 20:25 ` [PATCH v2 6/6] sugarbay: " nitin.a.kamble
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=1351125252.27553.64.camel@empanada \
--to=tom.zanussi@intel.com \
--cc=darren.hart@intel.com \
--cc=nitin.a.kamble@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.