From: John Weber <rjohnweber@gmail.com>
To: meta-freescale@yoctoproject.org
Subject: Re: [PATCH] Added support for the SolidRun HummingBird (also known as Carrier One)
Date: Wed, 08 Jan 2014 13:31:16 -0600 [thread overview]
Message-ID: <52CDA784.3060805@gmail.com> (raw)
In-Reply-To: <fe556181d2f94ae0aff9deb2b47aa72b@BY2PR03MB379.namprd03.prod.outlook.com>
On 1/7/14 9:46 AM, Daiane.Angolini@freescale.com wrote:
>
>> -----Original Message-----
>> From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-
>> bounces@yoctoproject.org] On Behalf Of Carlos Rafael Giani
>> Sent: Tuesday, January 07, 2014 1:35 PM
>> To: meta-freescale@yoctoproject.org
>> Subject: [meta-freescale] [PATCH] Added support for the SolidRun
>> HummingBird (also known as Carrier One)
>>
> Can you, please, send 3 different patches? One for machine file, one for
> u-boot and another one for kernel?
+1 to that.
>
> Please, use present in commit subject (Add support for SolidRun)
>
> It looks ugly that you called your machine file "hummingboard" but the
> Other reference in u-boot is cuboxi, is that right?
Will there be a U-boot for Cubox-i and a separate U-boot for Hummingboard?
If they will be the same (ideally), then I suggest that you call the recipe
u-boot-solidrun as they are both Solid-Run products. Same thing with the kernel
as well (linux-solidrun_3.0.35)
If not, then you would want to separate them out to u-boot-cuboxi and
u-boot-hummingboard (and with the kernel).
And please use savedefconfig to create a more condensed defconfig file for the
kernel.
next prev parent reply other threads:[~2014-01-08 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 15:35 [PATCH] Added support for the SolidRun HummingBird (also known as Carrier One) Carlos Rafael Giani
2014-01-07 15:38 ` [PATCH] Added support for the SolidRun HummingBird (also known as Carrier One) - applies to meta-fsl-arm-extra Carlos Rafael Giani
2014-01-07 15:46 ` [PATCH] Added support for the SolidRun HummingBird (also known as Carrier One) Daiane.Angolini
2014-01-08 19:31 ` John Weber [this message]
2014-01-07 15:51 ` Fabio Estevam
2014-01-17 21:40 ` Fabio Estevam
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=52CDA784.3060805@gmail.com \
--to=rjohnweber@gmail.com \
--cc=meta-freescale@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.