From: Tom Zanussi <tom.zanussi@intel.com>
To: nitin.a.kamble@intel.com
Cc: yocto@yoctoproject.org, darren.hart@intel.com
Subject: Re: [PATCH 3/6] crownbay README: add WebTitle & Compliance information
Date: Tue, 23 Oct 2012 16:16:16 -0500 [thread overview]
Message-ID: <1351026976.12186.70.camel@empanada> (raw)
In-Reply-To: <eafcdbdb3843e08adc7385d0f1cec2b316d1b691.1351023743.git.nitin.a.kamble@intel.com>
On Tue, 2012-10-23 at 13:24 -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-crownbay/README | 13 +++++++++++--
> 1 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/meta-crownbay/README b/meta-crownbay/README
> index 4bc9f31..3996a94 100644
> --- a/meta-crownbay/README
> +++ b/meta-crownbay/README
> @@ -2,13 +2,22 @@ This README file contains information on building the meta-crownbay
> BSP layer, and booting the images contained in the /binary directory.
> Please see the corresponding sections below for details.
>
> -The Crown Bay platform consists of the Intel Atom Z6xx processor,
> +The Crown Bay platform consists of the Intel Atom E6xx processor,
> plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
>
> It also supports the E6xx embedded on-chip graphics via the Intel
> Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
>
>
> +WebTitle: Intel Atom E6xx processor with Intel EG20T Controller Hub development kit (crownbay)
> +
I'm not sure this kind of thing should be in the README since we can
have multiple downloadable BSPs per layer e.g. crownbay vs
crownbay-noemgd. I suppose in keeping with the build system you could
have separate WebTitle_crownbay and WebTitle_crownbay-noemgd lines. ;-)
(and it would be nice if you could get rid of the CamelCaps too)
Why not put this info in the machine.conf, where we already have fields
meant to be machine parseable e.g.
#@TYPE: Machine
#@NAME: crownbay
#@WEBTITLE: ...
Or maybe just use the exisiting #@DESCRIPTION for that...
> +
> +Compliance:
> +============
For consistency with the rest of the README, please remove the colon and
clean up the underlining.
Thanks,
Tom
> +This BSP is compliant with Yocto Project as per requirements listed here:
> +http://www.yoctoproject.org/yocto-project-compatible-registration
> +
> +
> Dependencies
> ============
>
> @@ -22,7 +31,7 @@ This layer depends on:
> branch: master
>
> URI: git://git.yoctoproject.org/meta-intel
> - layers: intel
> + layers: meta-intel, meta-crownbay
> branch: master
>
>
next prev parent reply other threads:[~2012-10-23 21:16 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 [this message]
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
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=1351026976.12186.70.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.