From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs: rename Zynq defconfig files
Date: Thu, 31 Mar 2016 18:41:03 +0200 [thread overview]
Message-ID: <20160331184103.70f784bb@free-electrons.com> (raw)
In-Reply-To: <1456972732-9033-1-git-send-email-yamada.masahiro@socionext.com>
Hello,
On Thu, 3 Mar 2016 11:38:52 +0900, Masahiro Yamada wrote:
> These three are Zynq boards and the build procedure is almost the
> same. Having the SoC name prefix "zynq_" would be more consistent.
> Also, this is the way in which the Linux Device Trees and the U-Boot
> configuration files do.
>
> This commit renames as follows:
>
> zedboard_defconfig -> zynq_zed_defconfig
> microzed_defconfig -> zynq_microzed_defconfig
> xilinx_zc706_defconfig -> zynq_zc706_defconfig
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-03-31 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 2:38 [Buildroot] [PATCH] configs: rename Zynq defconfig files Masahiro Yamada
2016-03-31 16:41 ` Thomas Petazzoni [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=20160331184103.70f784bb@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