From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] DEVELOPERS: add csky developer
Date: Thu, 2 Mar 2017 11:42:20 +0100 [thread overview]
Message-ID: <20170302114220.141a883c@free-electrons.com> (raw)
In-Reply-To: <1488450842-29100-4-git-send-email-ren_guo@c-sky.com>
Hello,
On Thu, 2 Mar 2017 18:34:02 +0800, Guo Ren wrote:
> You can get more info from github.com/c-sky.
>
> Signed-off-by: Guo Ren <ren_guo@c-sky.com>
> ---
> DEVELOPERS | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/DEVELOPERS b/DEVELOPERS
> index 1bf07c3..cd4402f 100644
> --- a/DEVELOPERS
> +++ b/DEVELOPERS
> @@ -592,6 +592,11 @@ F: package/sdl2/
> N: Guillaume William Brs <guillaume.bressaix@gmail.com>
> F: package/liquid-dsp/
>
> +N: Guo Ren <ren_guo@c-sky.com>
> +F: arch/Config.in.csky
This should be part of the patch adding the architecture.
> +F: board/csky
> +F: configs/csky_*
And this of the patch adding the board.
But overall: this series looks almost good to go. I think the next
iteration will be OK. Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-02 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 10:33 [Buildroot] [PATCH 1/4] configs: add defconfig for Nationalchip gx6605s dev board Guo Ren
2017-03-02 10:34 ` [Buildroot] [PATCH 2/4] csky: Add new architecture Guo Ren
2017-03-02 10:34 ` [Buildroot] [PATCH 3/4] toolchain: only external toolchain option displayed Guo Ren
2017-03-02 10:41 ` Thomas Petazzoni
2017-03-02 10:34 ` [Buildroot] [PATCH 4/4] DEVELOPERS: add csky developer Guo Ren
2017-03-02 10:42 ` Thomas Petazzoni [this message]
2017-03-02 10:38 ` [Buildroot] [PATCH 1/4] configs: add defconfig for Nationalchip gx6605s dev board ren_guo
2017-03-02 10:40 ` Thomas Petazzoni
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=20170302114220.141a883c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox