From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org, rob.herring@linaro.org,
linux-omap@vger.kernel.org, arm@kernel.org
Subject: Re: [PATCH] ARM: omap: rework platform selection
Date: Mon, 16 Jun 2014 07:17:13 -0700 [thread overview]
Message-ID: <20140616141712.GL17845@atomide.com> (raw)
In-Reply-To: <20140616112610.GE17845@atomide.com>
* Tony Lindgren <tony@atomide.com> [140616 04:31]:
> * Arnd Bergmann <arnd@arndb.de> [140616 04:18]:
> >
> > Let's see if others have similar opinions Rob's patch as a whole.
> > I'd still like to keep all the parts aside from the OMAP change
> > and just back out the change that caused the problems.
> >
> > Does that seem reasonable to you?
>
> Yes makes sense to me if others don't have similar issues. I guess
> it should be possible to verify that by diffing the generated
> .config files compared to the old ones.
If you update Rob's patch and undo the omap2+ changes, you might
want to fold in something like the following to hide the omap
options behind a menu.
So far I have not come up with no great ideas on fixing this
properly short of requiring all omap .config files to add
CONFIG_ARCH_OMAP=y manually. Anybody got good ideas for that?
Regards,
Tony
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -1,3 +1,5 @@
+menu "TI OMAP/AM/DM/DRA Family"
+
config ARCH_OMAP
bool
@@ -342,3 +344,5 @@ config OMAP4_ERRATA_I688
endmenu
endif
+
+endmenu
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: rework platform selection
Date: Mon, 16 Jun 2014 07:17:13 -0700 [thread overview]
Message-ID: <20140616141712.GL17845@atomide.com> (raw)
In-Reply-To: <20140616112610.GE17845@atomide.com>
* Tony Lindgren <tony@atomide.com> [140616 04:31]:
> * Arnd Bergmann <arnd@arndb.de> [140616 04:18]:
> >
> > Let's see if others have similar opinions Rob's patch as a whole.
> > I'd still like to keep all the parts aside from the OMAP change
> > and just back out the change that caused the problems.
> >
> > Does that seem reasonable to you?
>
> Yes makes sense to me if others don't have similar issues. I guess
> it should be possible to verify that by diffing the generated
> .config files compared to the old ones.
If you update Rob's patch and undo the omap2+ changes, you might
want to fold in something like the following to hide the omap
options behind a menu.
So far I have not come up with no great ideas on fixing this
properly short of requiring all omap .config files to add
CONFIG_ARCH_OMAP=y manually. Anybody got good ideas for that?
Regards,
Tony
--- a/arch/arm/mach-omap2/Kconfig
+++ b/arch/arm/mach-omap2/Kconfig
@@ -1,3 +1,5 @@
+menu "TI OMAP/AM/DM/DRA Family"
+
config ARCH_OMAP
bool
@@ -342,3 +344,5 @@ config OMAP4_ERRATA_I688
endmenu
endif
+
+endmenu
next prev parent reply other threads:[~2014-06-16 14:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 10:04 [PATCH] ARM: omap: rework platform selection Arnd Bergmann
2014-06-16 10:04 ` Arnd Bergmann
2014-06-16 11:00 ` Tony Lindgren
2014-06-16 11:00 ` Tony Lindgren
2014-06-16 11:16 ` Arnd Bergmann
2014-06-16 11:16 ` Arnd Bergmann
2014-06-16 11:26 ` Tony Lindgren
2014-06-16 11:26 ` Tony Lindgren
2014-06-16 14:17 ` Tony Lindgren [this message]
2014-06-16 14:17 ` Tony Lindgren
2014-06-16 15:53 ` Rob Herring
2014-06-16 15:53 ` Rob Herring
2014-06-17 13:57 ` Arnd Bergmann
2014-06-17 13:57 ` Arnd Bergmann
2014-06-17 15:03 ` Rob Herring
2014-06-17 15:03 ` Rob Herring
2014-06-17 15:25 ` Tony Lindgren
2014-06-17 15:25 ` Tony Lindgren
2014-06-17 16:40 ` Rob Herring
2014-06-17 16:40 ` Rob Herring
2014-06-18 6:53 ` Tony Lindgren
2014-06-18 6:53 ` Tony Lindgren
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=20140616141712.GL17845@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rob.herring@linaro.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.