From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] board: rename ts to technologic
Date: Thu, 21 Apr 2016 23:06:29 +0200 [thread overview]
Message-ID: <20160421230629.45dc0009@free-electrons.com> (raw)
In-Reply-To: <1461255673-11443-2-git-send-email-damien.riegel@savoirfairelinux.com>
Hello,
On Thu, 21 Apr 2016 12:21:12 -0400, Damien Riegel wrote:
> Other projects, such as Linux [1] and U-Boot [2], use "technologic" for
> this manufacturer. To be more consistent across all of them, rename the
> board/ts folder to board/technologic.
>
> [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/vendor-prefixes.txt
> [2] http://git.denx.de/?p=u-boot.git;a=tree;f=board/technologic;hb=HEAD
>
> Signed-off-by: Damien Riegel <damien.riegel@savoirfairelinux.com>
> ---
> .../{ts => technologic}/ts5x00/fs-overlay/boot/syslinux/syslinux.cfg | 0
> board/{ts => technologic}/ts5x00/linux-3.17.config | 0
> board/{ts => technologic}/ts5x00/readme.txt | 0
> configs/ts5x00_defconfig | 4 ++--
> 4 files changed, 2 insertions(+), 2 deletions(-)
> rename board/{ts => technologic}/ts5x00/fs-overlay/boot/syslinux/syslinux.cfg (100%)
> rename board/{ts => technologic}/ts5x00/linux-3.17.config (100%)
> rename board/{ts => technologic}/ts5x00/readme.txt (100%)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-21 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 16:21 [Buildroot] [PATCH 0/2] add support for TS-4800 Damien Riegel
2016-04-21 16:21 ` [Buildroot] [PATCH 1/2] board: rename ts to technologic Damien Riegel
2016-04-21 21:06 ` Thomas Petazzoni [this message]
2016-04-21 16:21 ` [Buildroot] [PATCH 2/2] configs: add defconfig for TS-4800 Damien Riegel
2016-04-24 21:59 ` Thomas Petazzoni
2016-04-25 13:44 ` Damien Riegel
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=20160421230629.45dc0009@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