From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: OMAP3: cleanup AM35xx SoC detection
Date: Tue, 8 May 2012 13:58:22 -0700 [thread overview]
Message-ID: <20120508205822.GF5088@atomide.com> (raw)
In-Reply-To: <87zk9j5216.fsf@ti.com>
* Kevin Hilman <khilman@ti.com> [120507 10:37]:
> Tony,
>
> Kevin Hilman <khilman@ti.com> writes:
>
> > The detection of AM35xx SoCs is confusing and has redundancies. Clean
> > this up so that SoC detection is only based on SoC family: AM35xx.
>
> Since these aren't PM related, can you queue these with other cleanups
> for v3.5. This is now independent from the similar changes made to the
> clock fwk which Paul is queuing.
OK applied now to cleanup branch and just pushed out. Had to update them
a bit for the hwmod changes done by Paul.
> Once both series are merged, I'll have one final patch that removes all
> users of cpu_is_omap35*.
OK can you please do that one against the current cleanup branch at
commit a75bf667d6535af66d34f8d7be0a36aa2a96c56e?
Regards,
Tony
next prev parent reply other threads:[~2012-05-08 20:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 23:37 [PATCH 0/2] ARM: OMAP3: cleanup AM35xx SoC detection Kevin Hilman
2012-04-30 23:37 ` [PATCH 1/2] ARM: OMAP: AM35xx: remove redunant cpu_is checks for AM3505 Kevin Hilman
2012-04-30 23:37 ` [PATCH 2/2] ARM: OMAP: AM35xx: convert 3517 detection/flags to AM35xx Kevin Hilman
2012-05-08 22:15 ` Tony Lindgren
2012-05-07 17:33 ` [PATCH 0/2] ARM: OMAP3: cleanup AM35xx SoC detection Kevin Hilman
2012-05-08 20:58 ` Tony Lindgren [this message]
2012-05-08 21:17 ` Kevin Hilman
2012-05-08 22:17 ` 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=20120508205822.GF5088@atomide.com \
--to=tony@atomide.com \
--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;
as well as URLs for NNTP newsgroup(s).