From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: MACH_CPUIMX27 or MACH_EUKREA_CPUIMX27?
Date: Tue, 10 Jun 2014 16:35:09 +0200 [thread overview]
Message-ID: <1402410909.3798.32.camel@x220> (raw)
0) Summary: either the Kconfig symbol MACH_CPUIMX27 or the reference to
CONFIG_MACH_EUKREA_CPUIMX27 in arch/arm/tools/mach-types should probably
be renamed (once again).
1) An entry for CONFIG_MACH_CPUIMX27 was added to mach-types in v2.6.29.
2) The Kconfig symbol MACH_EUKREA_CPUIMX27 was added in v2.6.32.
3) That Kconfig symbol was renamed to MACH_CPUIMX27 in v2.6.34, too
match the reference in mach-types mentioned in 1).
4) But then the reference in mach-types was also renamed, to
MACH_EUKREA_CPUIMX27, in v3.1.
5) The net effect is that machine_is_eukrea_cpuimx27() equals 0 since
v3.1. That macro is used only once, in sound/soc/fsl/eukrea-tlv320.c. If
people still care about it then either the Kconfig symbol or the
reference in mach-types should be renamed.
Paul Bolle
next reply other threads:[~2014-06-10 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 14:35 Paul Bolle [this message]
2014-06-10 15:01 ` ARM: MACH_CPUIMX27 or MACH_EUKREA_CPUIMX27? Russell King - ARM Linux
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=1402410909.3798.32.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).