From: Tom Zanussi <tom.zanussi@intel.com>
To: nitin.a.kamble@intel.com
Cc: yocto@yoctoproject.org, darren.hart@intel.com
Subject: Re: [Patch v3 7/7] crownbay: add more information in README
Date: Thu, 25 Oct 2012 15:13:20 -0500 [thread overview]
Message-ID: <1351196000.27553.101.camel@empanada> (raw)
In-Reply-To: <b724623f2f22fdb2643a57ea4939831f54bd94e4.1351187270.git.nitin.a.kamble@intel.com>
On Thu, 2012-10-25 at 10:49 -0700, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>
> Mention Little Bay & Shell Bay boards from the crownbay kit
> in the readme.
>
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
> meta-crownbay/README | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/meta-crownbay/README b/meta-crownbay/README
> index 1f164f4..525b2e6 100644
> --- a/meta-crownbay/README
> +++ b/meta-crownbay/README
> @@ -5,6 +5,8 @@ Please see the corresponding sections below for details.
> The Crown Bay platform consists of the Intel Atom E6xx processor,
> plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
>
> +The crownbay kit consists of two boards, Shell Bay & Little Bay.
> +
This seems like a sort of random fact thrown in and doesn't explain what
Shell Bay or Little Bay are (and shouldn't it be Crown Bay kit to match,
instead of crownbay?).
I guess I'd like to see the text explaining the hardware fit together as
a whole and not just be a collection of facts about various aspects of
the hardware listed out randomly.
Tom
> It also supports the E6xx embedded on-chip graphics via the Intel
> Embedded Media and Graphics Driver (EMGD) 1.14 Driver.
>
next prev parent reply other threads:[~2012-10-26 4:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 17:49 [Patch v3 0/7] meta-intel README updates nitin.a.kamble
2012-10-25 17:49 ` [Patch v3 1/7] MAINTAINERS: correct pathname nitin.a.kamble
2012-10-25 17:49 ` [Patch v3 2/7] chiefriver: add WEBTITLE & Compliance information nitin.a.kamble
2012-10-25 17:49 ` [Patch v3 3/7] crownbay: " nitin.a.kamble
2012-10-25 17:49 ` [Patch v3 4/7] emenlow: " nitin.a.kamble
2012-10-25 17:49 ` [Patch v3 5/7] jasperforest: " nitin.a.kamble
2012-10-25 17:49 ` [Patch v3 6/7] sugarbay: " nitin.a.kamble
2012-10-25 17:49 ` [Patch v3 7/7] crownbay: add more information in README nitin.a.kamble
2012-10-25 20:13 ` Tom Zanussi [this message]
2012-10-25 20:14 ` [Patch v3 0/7] meta-intel README updates Tom Zanussi
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=1351196000.27553.101.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.