public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@ti.com>
Cc: hvaibhav@ti.com, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, paul@pwsan.com
Subject: Re: [PATCH-V5 0/3] Introducing TI's New SoC/board AM335XEVM
Date: Wed, 7 Dec 2011 13:10:29 -0800	[thread overview]
Message-ID: <20111207211029.GL31337@atomide.com> (raw)
In-Reply-To: <87y5up44bf.fsf@ti.com>

* Kevin Hilman <khilman@ti.com> [111206 15:52]:
> <hvaibhav@ti.com> writes:
> 
> > From: Vaibhav Hiremath <hvaibhav@ti.com>
> >
> > This patch set adds support for AM335x device having
> > Cortex-A8 MPU.
> >
> > Official website - http://www.ti.com/product/am3359
> >
> > AM335X is treated as another OMAP3 variant, where,
> > along with existing cpu class OMAP34XX, new cpu class AM33XX is created
> > and the respective type is AM335X, which is newly added device in
> > the family.
> > This means, cpu_is_omap34xx(), cpu_is_am33xx() and
> > cpu_is_am335x() checks return success for AM335X.
> >
> > Also, I have validated OMAP3 boot test with this patch-series on
> > OMAP3EVM.
> 
> Tony, this series looks good to me.
> 
> I've also tested it on a BeagleBone, so feel free to also add:
> 
> Tested-by: Kevin Hilman <khilman@ti.com>

Thanks looks good to me. We still need the machine_id update to
apply patches 2 and 3 in this series, so applying only the first
patch into soc branch for now.

Tony

  reply	other threads:[~2011-12-07 21:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  6:43 [PATCH-V5 0/3] Introducing TI's New SoC/board AM335XEVM hvaibhav
2011-12-07  0:24 ` Kevin Hilman
2011-12-07 21:10   ` Tony Lindgren [this message]
2011-12-08 13:45     ` Hiremath, Vaibhav
2011-12-08 17:18       ` Tony Lindgren
2012-02-01  6:53         ` Hiremath, Vaibhav
2012-01-18  8:47     ` 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=20111207211029.GL31337@atomide.com \
    --to=tony@atomide.com \
    --cc=hvaibhav@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox