From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Pedanekar, Hemant" <hemantp@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"khilman@deeprootsystems.com" <khilman@deeprootsystems.com>
Subject: Re: [PATCH v3 1/4] TI816X: Update common omap platform files
Date: Tue, 4 Jan 2011 15:25:47 -0800 [thread overview]
Message-ID: <20110104232547.GP7771@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101041046540.9203@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [110104 09:48]:
> On Tue, 4 Jan 2011, Pedanekar, Hemant wrote:
>
> > Looking at above, it seems another config option like
> > CONFIG_SOC_OMAP3XXX is also needed in addition to CONFIG_SOC_OMAPTI816X.
>
> We already have CONFIG_ARCH_OMAP3430, CONFIG_ARCH_OMAP2430, and
> CONFIG_ARCH_OMAP2420. I guess at some point those need to be renamed to
> CONFIG_SOC_*.
Yes that's what I was thinking too. Keep CONFIG_ARCH_OMAP2, 3, and 4,
and rename CONFIG_ARCH_OMAP3430 etc to CONFIG_SO_COMAP3430 and so on.
Regards,
Tony
next prev parent reply other threads:[~2011-01-04 23:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 17:28 [PATCH v3 1/4] TI816X: Update common omap platform files Hemant Pedanekar
2011-01-03 23:07 ` Paul Walmsley
2011-01-04 1:50 ` Tony Lindgren
2011-01-04 17:38 ` Pedanekar, Hemant
2011-01-04 17:49 ` Paul Walmsley
2011-01-04 23:25 ` Tony Lindgren [this message]
2011-01-04 23:57 ` [PATCH] omap: Start using CONFIG_SOC_OMAP (Re: [PATCH v3 1/4] TI816X: Update common omap platform files) Tony Lindgren
2011-01-05 1:22 ` [PATCH v3 1/4] TI816X: Update common omap platform files Pedanekar, Hemant
2011-01-05 23:59 ` Pedanekar, Hemant
2011-01-07 2:56 ` 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=20110104232547.GP7771@atomide.com \
--to=tony@atomide.com \
--cc=hemantp@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
/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.