From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: imx: remove MACH_MXLADS
Date: Mon, 17 Feb 2014 10:02:48 +0100 [thread overview]
Message-ID: <1392627768.10966.23.camel@x220> (raw)
In-Reply-To: <1392612187.657010375@f87.i.mail.ru>
On Mon, 2014-02-17 at 08:43 +0400, Alexander Shiyan wrote:
> It seems that even in the current state, Kconfig for i.MX contains an error.
> As a start, we should rename ARCH_MX1ADS to MACH_MX1ADS first.
Last year I admitted that I didn't entirely grasped the differences
between "arch", "platform", and "machine" in the arch/arm universe[1].
Perhaps someone could help me understand why it's better to use
MACH_MX1ADS here.
Paul Bolle
[1] http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2013-May/038204.html
next prev parent reply other threads:[~2014-02-17 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 18:03 [PATCH] arm: imx: remove MACH_MXLADS Paul Bolle
2014-02-16 18:16 ` Alexander Shiyan
2014-02-16 18:43 ` Paul Bolle
2014-02-16 19:06 ` Alexander Shiyan
2014-02-16 19:12 ` Paul Bolle
2014-02-16 19:21 ` Alexander Shiyan
2014-02-16 20:35 ` Paul Bolle
2014-02-17 4:43 ` Alexander Shiyan
2014-02-17 9:02 ` Paul Bolle [this message]
2014-02-17 9:18 ` Sascha Hauer
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=1392627768.10966.23.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