From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Lucas Dutra Nunes <ldnunes@ossystems.com.br>,
meta-freescale@yoctoproject.org
Subject: Re: [meta-fsl-arm-extra][PATCH 1/3] linux-boundary: move nitrogen6x defconfig to machine dir
Date: Sun, 06 Oct 2013 08:23:09 -0700 [thread overview]
Message-ID: <5251805D.7010905@boundarydevices.com> (raw)
In-Reply-To: <1381002356-13268-1-git-send-email-ldnunes@ossystems.com.br>
Thanks Luca,
On 10/05/2013 12:45 PM, Lucas Dutra Nunes wrote:
> The move is necessary to add support for the nitrogen6x-lite board.
>
> Change-Id: I146e2a871b4e73f581cadd536ec03452a3756b2f
> Signed-off-by: Lucas Dutra Nunes <ldnunes@ossystems.com.br>
> ---
> .../linux/linux-boundary-3.0.35/defconfig | 270 --------------------
> .../linux-boundary-3.0.35/nitrogen6x/defconfig | 270 ++++++++++++++++++++
> 2 files changed, 270 insertions(+), 270 deletions(-)
> delete mode 100644 recipes-kernel/linux/linux-boundary-3.0.35/defconfig
> create mode 100644 recipes-kernel/linux/linux-boundary-3.0.35/nitrogen6x/defconfig
>
For the series:
Tested-by: Eric Nelson <eric.nelson@boundarydevices.com>
Acked-by: Eric Nelson <eric.nelson@boundarydevices.com>
I tested this out using fsl-image-gui on the nitrogen6x and
core-image-minimal on nitrogen6x-lite.
Regards,
Eric
prev parent reply other threads:[~2013-10-06 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 19:45 [meta-fsl-arm-extra][PATCH 1/3] linux-boundary: move nitrogen6x defconfig to machine dir Lucas Dutra Nunes
2013-10-05 19:45 ` [meta-fsl-arm-extra][PATCH 2/3] linux-boundary: add nitrogen6x-lite defconfig Lucas Dutra Nunes
2013-10-05 19:45 ` [meta-fsl-arm-extra][PATCH 3/3] nitrogen6x-lite: add machine definition Lucas Dutra Nunes
2013-10-06 15:23 ` Eric Nelson [this message]
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=5251805D.7010905@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=ldnunes@ossystems.com.br \
--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.