From: Tony Lindgren <tony@atomide.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP: drop "select MACH_NOKIA_RM696"
Date: Fri, 8 Mar 2013 10:10:29 -0800 [thread overview]
Message-ID: <20130308181029.GF11806@atomide.com> (raw)
In-Reply-To: <1362765764.5994.87.camel@x61.thuisdomein>
* Paul Bolle <pebolle@tiscali.nl> [130308 10:06]:
> On Fri, 2013-03-08 at 09:55 -0800, Tony Lindgren wrote:
> > * Paul Bolle <pebolle@tiscali.nl> [130308 09:24]:
> > > Should I draft a patch?
> >
> > Sure that would be nice.
>
> One thing I couldn't determine is how the generated mach-types.h header
> handles multiple CONFIG_MACH_* macros.
>
> If both CONFIG_MACH_FOO and CONFIG_MACH_BAR are defined, and these both
> have a line in */mach-types, will the machine_is_foo() and
> machine_is_bar() macros both behave as one would expect?
Yes they do, for the selected ones the macro becomes
machine_arch_type == MACH_TYPE_XYZ instead of 0.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP: drop "select MACH_NOKIA_RM696"
Date: Fri, 8 Mar 2013 10:10:29 -0800 [thread overview]
Message-ID: <20130308181029.GF11806@atomide.com> (raw)
In-Reply-To: <1362765764.5994.87.camel@x61.thuisdomein>
* Paul Bolle <pebolle@tiscali.nl> [130308 10:06]:
> On Fri, 2013-03-08 at 09:55 -0800, Tony Lindgren wrote:
> > * Paul Bolle <pebolle@tiscali.nl> [130308 09:24]:
> > > Should I draft a patch?
> >
> > Sure that would be nice.
>
> One thing I couldn't determine is how the generated mach-types.h header
> handles multiple CONFIG_MACH_* macros.
>
> If both CONFIG_MACH_FOO and CONFIG_MACH_BAR are defined, and these both
> have a line in */mach-types, will the machine_is_foo() and
> machine_is_bar() macros both behave as one would expect?
Yes they do, for the selected ones the macro becomes
machine_arch_type == MACH_TYPE_XYZ instead of 0.
Regards,
Tony
next prev parent reply other threads:[~2013-03-08 18:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 10:29 [PATCH] ARM: OMAP: drop "select MACH_NOKIA_RM696" Paul Bolle
2013-03-08 10:29 ` Paul Bolle
2013-03-08 16:11 ` Aaro Koskinen
2013-03-08 16:11 ` Aaro Koskinen
2013-03-08 16:35 ` Tony Lindgren
2013-03-08 16:35 ` Tony Lindgren
2013-03-08 17:20 ` Paul Bolle
2013-03-08 17:20 ` Paul Bolle
2013-03-08 17:55 ` Tony Lindgren
2013-03-08 17:55 ` Tony Lindgren
2013-03-08 18:02 ` Paul Bolle
2013-03-08 18:02 ` Paul Bolle
2013-03-08 18:10 ` Tony Lindgren [this message]
2013-03-08 18:10 ` Tony Lindgren
2013-03-09 0:01 ` Russell King - ARM Linux
2013-03-09 0:01 ` Russell King - ARM Linux
2013-03-09 19:48 ` Paul Bolle
2013-03-09 19:48 ` Paul Bolle
2013-03-11 16:33 ` Tony Lindgren
2013-03-11 16:33 ` Tony Lindgren
2013-03-14 8:00 ` Paul Bolle
2013-03-14 8:00 ` Paul Bolle
2013-03-08 17:18 ` Paul Bolle
2013-03-08 17:18 ` Paul Bolle
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=20130308181029.GF11806@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pebolle@tiscali.nl \
/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.