From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH] ARM: OMAP2+: am33xx: Make am33xx as a separate class
Date: Tue, 10 Jul 2012 01:43:35 -0700 [thread overview]
Message-ID: <20120710084335.GP1122@atomide.com> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83EA699EE@DBDE01.ent.ti.com>
* Hiremath, Vaibhav <hvaibhav@ti.com> [120710 01:43]:
>
> Can we clean these branches; it is very confusing to track with so many
> multiple versions?
Yeah I'll drop some after the merge window..
> Also, One patch still has not merged is,
>
> [PATCH-V2] ARM: OMAP: cpu: Make cpu_class_is_omap2 true for all non-omap1 platforms
>
> Do you have any comments on this? If not, can you merge it?
Posted some comments on it, we need to fix that properly for v3.7
merge window.
Tony
next prev parent reply other threads:[~2012-07-10 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 13:00 [RESEND PATCH] ARM: OMAP2+: am33xx: Change cpu_is_am33xx to soc_is_am33xx Vaibhav Hiremath
2012-07-03 13:00 ` [RESEND PATCH] ARM: OMAP2+: am33xx: Make am33xx as a separate class Vaibhav Hiremath
2012-07-04 7:24 ` Tony Lindgren
2012-07-04 8:15 ` Tony Lindgren
2012-07-05 15:27 ` Tony Lindgren
2012-07-10 8:38 ` Hiremath, Vaibhav
2012-07-10 8:43 ` Tony Lindgren [this message]
2012-07-04 10:26 ` Hiremath, Vaibhav
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=20120710084335.GP1122@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).