From: shc_work@mail.ru (Alexander Shiyan)
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm: imx: remove MACH_MXLADS
Date: Sun, 16 Feb 2014 23:21:04 +0400 [thread overview]
Message-ID: <1392578464.996901773@f49.i.mail.ru> (raw)
In-Reply-To: <1392577965.28866.37.camel@x220>
???????????, 16 ??????? 2014, 20:12 +01:00 ?? Paul Bolle <pebolle@tiscali.nl>:
> On Sun, 2014-02-16 at 23:06 +0400, Alexander Shiyan wrote:
> > Kconfig selects MACH_MXLADS, this enables machine_arch_type
> > from include/generated/mach-types.h which used for machine_is_xx() macro,
> > so if multiple boards is defined in the kernel, this cause to incorrect
> matching.
>
> But, as I stated in the commit explanation, there are no users of
> machine_is_mxlads().
If you have MXLADS and FOO boards support in the kernel (for example)
and you want to start MXLADS version, your machine_is_FOO() will be positive,
since machine_arch_type will be constant value FOO in this case.
---
WARNING: multiple messages have this Message-ID (diff)
From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Paul Bolle" <pebolle@tiscali.nl>
Cc: "Russell King" <linux@arm.linux.org.uk>,
"Richard Weinberger" <richard@nod.at>,
linux-kernel@vger.kernel.org,
"Sascha Hauer" <kernel@pengutronix.de>,
"Shawn Guo" <shawn.guo@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm: imx: remove MACH_MXLADS
Date: Sun, 16 Feb 2014 23:21:04 +0400 [thread overview]
Message-ID: <1392578464.996901773@f49.i.mail.ru> (raw)
In-Reply-To: <1392577965.28866.37.camel@x220>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 863 bytes --]
ÐоÑкÑеÑенÑе, 16 ÑевÑÐ°Ð»Ñ 2014, 20:12 +01:00 Ð¾Ñ Paul Bolle <pebolle@tiscali.nl>:
> On Sun, 2014-02-16 at 23:06 +0400, Alexander Shiyan wrote:
> > Kconfig selects MACH_MXLADS, this enables machine_arch_type
> > from include/generated/mach-types.h which used for machine_is_xx() macro,
> > so if multiple boards is defined in the kernel, this cause to incorrect
> matching.
>
> But, as I stated in the commit explanation, there are no users of
> machine_is_mxlads().
If you have MXLADS and FOO boards support in the kernel (for example)
and you want to start MXLADS version, your machine_is_FOO() will be positive,
since machine_arch_type will be constant value FOO in this case.
---
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2014-02-16 19:21 UTC|newest]
Thread overview: 20+ 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:03 ` Paul Bolle
2014-02-16 18:16 ` Alexander Shiyan
2014-02-16 18:16 ` Alexander Shiyan
2014-02-16 18:43 ` Paul Bolle
2014-02-16 18:43 ` Paul Bolle
2014-02-16 19:06 ` Alexander Shiyan
2014-02-16 19:06 ` Alexander Shiyan
2014-02-16 19:12 ` Paul Bolle
2014-02-16 19:12 ` Paul Bolle
2014-02-16 19:21 ` Alexander Shiyan [this message]
2014-02-16 19:21 ` Alexander Shiyan
2014-02-16 20:35 ` Paul Bolle
2014-02-16 20:35 ` Paul Bolle
2014-02-17 4:43 ` Alexander Shiyan
2014-02-17 4:43 ` Alexander Shiyan
2014-02-17 9:02 ` Paul Bolle
2014-02-17 9:02 ` Paul Bolle
2014-02-17 9:18 ` Sascha Hauer
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=1392578464.996901773@f49.i.mail.ru \
--to=shc_work@mail.ru \
--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 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.