From: Pavel Machek <pavel@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 04/21] ARM: tegra: collect SoC sources into mach-tegra
Date: Wed, 28 Jan 2015 17:39:53 +0100 [thread overview]
Message-ID: <20150128163953.GA20594@amd> (raw)
In-Reply-To: <54C67C29.3040401@wwwdotorg.org>
On Mon 2015-01-26 10:40:57, Stephen Warren wrote:
> On 01/24/2015 11:11 PM, Masahiro Yamada wrote:
> >This commit moves files as follows:
> >
> > arch/arm/cpu/arm720t/tegra20/* -> arch/arm/mach-tegra/tegra20/*
> > arch/arm/cpu/arm720t/tegra30/* -> arch/arm/mach-tegra/tegra30/*
> ...
>
> Bikeshed: I know that this matches what the Linux kernel has for 32-bit ARM,
> but I've always disliked using the word "machine" to describe an SoC. Would
> just "tegra" or "soc-tegra" be better than "mach-tegra"? Feel free to
> entirely ignore this though; I don't feel too strongly.
Please keep it consistent with Linux.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-01-28 16:39 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 6:11 [U-Boot] [RFC PATCH 0/21] ARM: start to move SoC code into arch/arm/mach-* Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 01/21] ARM: at91: move board select menu and common settings Masahiro Yamada
2015-01-26 10:13 ` Andreas Bießmann
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 02/21] ARM: prepare for moving SoC sources into mach-* Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 03/21] ARM: at91: collect SoC sources into mach-at91 Masahiro Yamada
2015-01-26 10:09 ` Andreas Bießmann
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 04/21] ARM: tegra: collect SoC sources into mach-tegra Masahiro Yamada
2015-01-26 15:26 ` Simon Glass
2015-01-26 17:40 ` Stephen Warren
2015-01-28 2:11 ` Masahiro Yamada
2015-02-03 21:49 ` Tom Rini
2015-01-28 16:39 ` Pavel Machek [this message]
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 05/21] ARM: UniPhier: move SoC sources to mach-uniphier Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 06/21] ARM: davinci: move SoC sources to mach-davinci Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 07/21] ARM: kirkwood: move SOC sources to mach-kirkwood Masahiro Yamada
2015-01-26 10:17 ` Stefan Roese
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 08/21] ARM: nomadik: move SoC sources to mach-nomadik Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 09/21] ARM: highbank: move SoC sources to mach-highbank Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 10/21] ARM: orion5x: move SoC sources to mach-orion5x Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 11/21] ARM: versatile: move SoC sources to mach-versatile Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 12/21] ARM: keystone: move SoC sources to mach-keystone Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 13/21] kbuild: prepare for moving headers into mach-*/include/mach Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 14/21] ARM: at91: move SoC headers to mach-at91/include/mach Masahiro Yamada
2015-01-26 10:07 ` Andreas Bießmann
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 15/21] ARM: UniPhier: move SoC headers to mach-uniphier/include/mach Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 16/21] ARM: davinci: move SoC headers to mach-davinci/include/mach Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 17/21] ARM: kirkwood: move SoC headers to mach-kirkwood/include/mach Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 18/21] ARM: nomadik: move SoC headers to mach-nomadik/include/mach Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 19/21] ARM: orion5x: move SoC headers to mach-orion5x/include/mach Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 20/21] ARM: keystone: move SoC headers to mach-keystone/include/mach Masahiro Yamada
2015-01-25 6:11 ` [U-Boot] [RFC PATCH 21/21] ARM: prepare for including <mach/*.h> Masahiro Yamada
2015-02-01 3:02 ` [U-Boot] [RFC PATCH 0/21] ARM: start to move SoC code into arch/arm/mach-* Albert ARIBAUD
2015-02-01 3:20 ` Simon Glass
2015-02-01 10:11 ` Albert ARIBAUD
2015-02-01 16:23 ` Simon Glass
2015-02-03 7:42 ` Albert ARIBAUD
2015-02-02 3:33 ` Masahiro Yamada
2015-02-02 17:18 ` Stephen Warren
2015-02-04 13:52 ` Pavel Machek
2015-02-05 3:08 ` Simon Glass
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=20150128163953.GA20594@amd \
--to=pavel@denx.de \
--cc=u-boot@lists.denx.de \
/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.