From: Vishwanath Sripathy <vishwanath.bs@ti.com>
To: Kevin Hilman <khilman@ti.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com, Nishanth Menon <nm@ti.com>
Subject: RE: [PATCHV2] OMAP4: OPP: add OMAP4460 definitions
Date: Wed, 20 Jul 2011 23:00:32 +0530 [thread overview]
Message-ID: <cf569df6d3275b4143c3b350ff5e2bf5@mail.gmail.com> (raw)
In-Reply-To: <87wrfejo63.fsf@ti.com>
Kevin,
> -----Original Message-----
> From: Kevin Hilman [mailto:khilman@ti.com]
> Sent: Tuesday, July 19, 2011 8:47 PM
> To: Vishwanath Sripathy
> Cc: linux-omap@vger.kernel.org; paul@pwsan.com; Nishanth Menon
> Subject: Re: [PATCHV2] OMAP4: OPP: add OMAP4460 definitions
>
> Vishwanath Sripathy <vishwanath.bs@ti.com> writes:
>
> > I see that this patch is not queued for 3.1 merge window. Any
> > issues/comments on this patch?
>
> I did not look at this patch as it came late in the development
> cycle.
>
> A quick glance now suggests it has a few minor problems.
>
> - patch was not Cc's to linux-arm-kernel
> - uses 44XX naming which is not used in l-o master
Sorry I did not get this point. What do you mean by 44XX naming?
I applied this patch against lo master and it seems to apply and compile
perfectly fine.
Vishwa
>
> Please update against current l-o tree which has the PRCM/hwmod
> updates
> from Paul/Benoit as well as the base 4460 support for v3.1.
>
> Kevin
next prev parent reply other threads:[~2011-07-20 17:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 5:40 [PATCHV2] OMAP4: OPP: add OMAP4460 definitions Vishwanath BS
2011-07-19 13:25 ` Vishwanath Sripathy
2011-07-19 15:16 ` Kevin Hilman
2011-07-20 17:30 ` Vishwanath Sripathy [this message]
2011-07-21 0:04 ` Kevin Hilman
[not found] <yes>
2011-07-21 4:54 ` Vishwanath BS
2011-07-21 4:54 ` Vishwanath BS
[not found] ` <4e27b0d0.100e8e0a.43e0.ffffe6d9SMTPIN_ADDED@mx.google.com>
2011-07-21 4:56 ` Vishwanath Sripathy
2011-07-21 4:56 ` Vishwanath Sripathy
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=cf569df6d3275b4143c3b350ff5e2bf5@mail.gmail.com \
--to=vishwanath.bs@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--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.