From: Darren Hart <darren.hart@intel.com>
To: nitin.a.kamble@intel.com
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 6/6] sugarbay README: add WebTitle & Compliance information
Date: Tue, 23 Oct 2012 13:49:23 -0700 [thread overview]
Message-ID: <508702D3.2030700@intel.com> (raw)
In-Reply-To: <4f441c599bd74b28f63f170a49f550236fe27c3c.1351023743.git.nitin.a.kamble@intel.com>
On 10/23/2012 01:24 PM, 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-sugarbay/README | 9 ++++++++-
> 1 files changed, 8 insertions(+), 1 deletions(-)
>
> diff --git a/meta-sugarbay/README b/meta-sugarbay/README
> index c8a99d7..36da170 100644
> --- a/meta-sugarbay/README
> +++ b/meta-sugarbay/README
> @@ -6,6 +6,13 @@ The 'Sugar Bay' platform consists of the Intel Sandy Bridge processor,
> plus the Cougar Point PCH (Q67 Express or B65 Express chipsets). This
> BSP assumes that the Sandy Bridge integrated graphics are being used.
>
> +WebTitle: Intel 2nd Generations Core Platforms: Core i3, i5, i7 (Sandy Bridge)
Some places you used merged lowercase terms "crownbay" and other places
the capitalized expanded terms "Sandy Bridge". I don't know which is more
correct, but we should be consistent in our usage.
--
Darren
> +
> +Compliance:
> +============
> +This BSP is compliant with Yocto Project as per requirements listed here:
> +http://www.yoctoproject.org/yocto-project-compatible-registration
> +
>
> Dependencies
> ============
> @@ -20,7 +27,7 @@ This layer depends on:
> branch: master
>
> URI: git://git.yoctoproject.org/meta-intel
> - layers: intel
> + layers: meta-intel, meta-sugarbay
> branch: master
>
>
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-10-23 20:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 20:24 [PATCH 0/6] meta-intel: README updates nitin.a.kamble
2012-10-23 20:24 ` [PATCH 1/6] MAINTAINERS: corect pathname nitin.a.kamble
2012-10-23 20:24 ` [PATCH 2/6] chiefriver README: add WebTitle & Compliance information nitin.a.kamble
2012-10-23 20:46 ` Darren Hart
2012-10-23 20:24 ` [PATCH 3/6] crownbay " nitin.a.kamble
2012-10-23 20:47 ` Darren Hart
2012-10-24 20:22 ` Kamble, Nitin A
2012-10-23 21:16 ` Tom Zanussi
2012-10-23 21:21 ` Darren Hart
2012-10-24 16:06 ` Kamble, Nitin A
2012-10-24 16:43 ` Tom Zanussi
2012-10-24 17:06 ` Darren Hart
2012-10-24 18:12 ` Kamble, Nitin A
2012-10-24 18:15 ` Sean Liming
2012-10-24 18:37 ` Kamble, Nitin A
2012-10-24 19:15 ` Sean Liming
2012-10-24 19:26 ` Tom Zanussi
2012-10-23 20:24 ` [PATCH 4/6] emenlow " nitin.a.kamble
2012-10-23 20:24 ` [PATCH 5/6] jasperforest " nitin.a.kamble
2012-10-23 20:24 ` [PATCH 6/6] sugarbay " nitin.a.kamble
2012-10-23 20:49 ` Darren Hart [this message]
2012-10-23 20:27 ` [PATCH 0/6] meta-intel: README updates Kamble, Nitin A
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=508702D3.2030700@intel.com \
--to=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.