From: "Hiremath, Vaibhav" <hvaibhav@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Paul Walmsley <paul@pwsan.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Hilman, Kevin" <khilman@ti.com>,
"Nayak, Rajendra" <rnayak@ti.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH-V4 0/4] ARM: OMAP2+: Add voltagedomain, powerdomain & PRM support for AM33XX device
Date: Thu, 26 Apr 2012 18:49:12 +0000 [thread overview]
Message-ID: <79CD15C6BA57404B839C016229A409A83E9FF9EA@DBDE01.ent.ti.com> (raw)
In-Reply-To: <20120426184312.GY3739@atomide.com>
On Fri, Apr 27, 2012 at 00:13:13, Tony Lindgren wrote:
> * Hiremath, Vaibhav <hvaibhav@ti.com> [120423 11:31]:
> > On Thu, Apr 19, 2012 at 04:48:37, Tony Lindgren wrote:
> > > * Hiremath, Vaibhav <hvaibhav@ti.com> [120413 03:39]:
> > > > On Thu, Apr 12, 2012 at 13:56:06, Paul Walmsley wrote:
> > > >
> > > > Yes, we are using am3517evm file for AM33XX MACHINE_INIT definition here.
> > > > These patches have been reviewed and accepted in the list, only thing is
> > > > they couldn't make it to upstream during v3.4 merge window.
> > > >
> > > > I believe Tony is going to push them for v3.5 now.
> > >
> > > Hmm care to clarify which patches are you talking about here?
> > >
> >
> > Tony,
> > I was referring to initial 2 baseport patches which we have dropped due
> > dependency on mach-types.
> >
> > arm:omap:am33xx: Add AM335XEVM machine support
> > arm:omap:am33xx: Add low level debugging support
>
> Can you please repost these against current v3.4-rc4?
>
Ok, I will do that.
> > One patch (which was independent) from this series, made its way to upstream,
> > ARM: OMAP2+: id: Add am33xx SoC type detection
>
> OK
>
> > Can you please make sure that, it gets included into your next pull request?
>
> As far as I remember they looked OK for minimal board changes.
>
Yes, they were accepted and were also available under linux-omap/soc2 branch
for quite some time.
Thanks,
Vaibhav
WARNING: multiple messages have this Message-ID (diff)
From: hvaibhav@ti.com (Hiremath, Vaibhav)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH-V4 0/4] ARM: OMAP2+: Add voltagedomain, powerdomain & PRM support for AM33XX device
Date: Thu, 26 Apr 2012 18:49:12 +0000 [thread overview]
Message-ID: <79CD15C6BA57404B839C016229A409A83E9FF9EA@DBDE01.ent.ti.com> (raw)
In-Reply-To: <20120426184312.GY3739@atomide.com>
On Fri, Apr 27, 2012 at 00:13:13, Tony Lindgren wrote:
> * Hiremath, Vaibhav <hvaibhav@ti.com> [120423 11:31]:
> > On Thu, Apr 19, 2012 at 04:48:37, Tony Lindgren wrote:
> > > * Hiremath, Vaibhav <hvaibhav@ti.com> [120413 03:39]:
> > > > On Thu, Apr 12, 2012 at 13:56:06, Paul Walmsley wrote:
> > > >
> > > > Yes, we are using am3517evm file for AM33XX MACHINE_INIT definition here.
> > > > These patches have been reviewed and accepted in the list, only thing is
> > > > they couldn't make it to upstream during v3.4 merge window.
> > > >
> > > > I believe Tony is going to push them for v3.5 now.
> > >
> > > Hmm care to clarify which patches are you talking about here?
> > >
> >
> > Tony,
> > I was referring to initial 2 baseport patches which we have dropped due
> > dependency on mach-types.
> >
> > arm:omap:am33xx: Add AM335XEVM machine support
> > arm:omap:am33xx: Add low level debugging support
>
> Can you please repost these against current v3.4-rc4?
>
Ok, I will do that.
> > One patch (which was independent) from this series, made its way to upstream,
> > ARM: OMAP2+: id: Add am33xx SoC type detection
>
> OK
>
> > Can you please make sure that, it gets included into your next pull request?
>
> As far as I remember they looked OK for minimal board changes.
>
Yes, they were accepted and were also available under linux-omap/soc2 branch
for quite some time.
Thanks,
Vaibhav
next prev parent reply other threads:[~2012-04-26 18:49 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 16:03 [PATCH-V4 0/4] ARM: OMAP2+: Add voltagedomain, powerdomain & PRM support for AM33XX device Vaibhav Hiremath
2012-03-30 16:03 ` Vaibhav Hiremath
2012-03-30 16:03 ` [PATCH-V4 1/4] ARM: OMAP3+: am33xx: Add voltage domain data Vaibhav Hiremath
2012-03-30 16:03 ` Vaibhav Hiremath
2012-04-28 0:39 ` Paul Walmsley
2012-04-28 0:39 ` Paul Walmsley
2012-04-30 20:41 ` Kevin Hilman
2012-04-30 20:41 ` Kevin Hilman
2012-03-30 16:03 ` [PATCH-V4 2/4] ARM: OMAP3/4: omap_hwmod: Add rstst_off field to struct omap_hwmod_omap4_prcm Vaibhav Hiremath
2012-03-30 16:03 ` Vaibhav Hiremath
2012-05-29 6:31 ` Hiremath, Vaibhav
2012-05-29 6:31 ` Hiremath, Vaibhav
2012-03-30 16:03 ` [PATCH-V4 3/4] ARM: OMAP2+: powerdomain: Add offset & mask fields to struct powerdomain Vaibhav Hiremath
2012-03-30 16:03 ` Vaibhav Hiremath
2012-03-30 16:03 ` [PATCH-V4 4/4] ARM: OMAP3+: am33xx: Add powerdomain & PRM support Vaibhav Hiremath
2012-03-30 16:03 ` Vaibhav Hiremath
2012-04-27 0:49 ` Kevin Hilman
2012-04-27 0:49 ` Kevin Hilman
2012-04-27 6:37 ` Hiremath, Vaibhav
2012-04-27 6:37 ` Hiremath, Vaibhav
2012-05-04 18:43 ` Tony Lindgren
2012-05-04 18:43 ` Tony Lindgren
2012-04-27 20:44 ` Kevin Hilman
2012-04-27 20:44 ` Kevin Hilman
2012-03-30 16:22 ` [PATCH-V4 0/4] ARM: OMAP2+: Add voltagedomain, powerdomain & PRM support for AM33XX device Hiremath, Vaibhav
2012-03-30 16:22 ` Hiremath, Vaibhav
2012-04-12 8:26 ` Paul Walmsley
2012-04-12 8:26 ` Paul Walmsley
2012-04-13 10:36 ` Hiremath, Vaibhav
2012-04-13 10:36 ` Hiremath, Vaibhav
2012-04-13 10:43 ` Paul Walmsley
2012-04-13 10:43 ` Paul Walmsley
2012-04-16 7:18 ` Hiremath, Vaibhav
2012-04-16 7:18 ` Hiremath, Vaibhav
2012-04-18 23:21 ` Tony Lindgren
2012-04-18 23:21 ` Tony Lindgren
2012-04-18 23:18 ` Tony Lindgren
2012-04-18 23:18 ` Tony Lindgren
2012-04-23 18:28 ` Hiremath, Vaibhav
2012-04-23 18:28 ` Hiremath, Vaibhav
2012-04-26 18:43 ` Tony Lindgren
2012-04-26 18:43 ` Tony Lindgren
2012-04-26 18:49 ` Hiremath, Vaibhav [this message]
2012-04-26 18:49 ` Hiremath, Vaibhav
2012-04-26 19:05 ` Tony Lindgren
2012-04-26 19:05 ` Tony Lindgren
2012-04-27 8:53 ` Hiremath, Vaibhav
2012-04-27 8:53 ` Hiremath, Vaibhav
2012-05-02 9:09 ` Paul Walmsley
2012-05-02 9:09 ` Paul Walmsley
2012-05-07 10:32 ` Cousson, Benoit
2012-05-07 10:32 ` Cousson, Benoit
2012-05-07 10:44 ` Shilimkar, Santosh
2012-05-07 10:44 ` Shilimkar, Santosh
2012-05-07 13:59 ` Hiremath, Vaibhav
2012-05-07 13:59 ` Hiremath, Vaibhav
2012-05-02 9:30 ` Paul Walmsley
2012-05-02 9:30 ` Paul Walmsley
2012-05-02 9:37 ` Hiremath, Vaibhav
2012-05-02 9:37 ` Hiremath, Vaibhav
2012-05-03 14:44 ` Hiremath, Vaibhav
2012-05-03 14:44 ` Hiremath, Vaibhav
2012-04-25 13:44 ` Hiremath, Vaibhav
2012-04-25 13:44 ` 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=79CD15C6BA57404B839C016229A409A83E9FF9EA@DBDE01.ent.ti.com \
--to=hvaibhav@ti.com \
--cc=b-cousson@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=tony@atomide.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.