From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Nayak, Rajendra" <rnayak@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 00/06] OMAP3430 Errata, defect fixes and optimizations
Date: Thu, 04 Jun 2009 16:31:01 -0700 [thread overview]
Message-ID: <87oct3d1ai.fsf@deeprootsystems.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB03057E76B6@dbde02.ent.ti.com> (Rajendra Nayak's message of "Thu\, 28 May 2009 18\:13\:00 +0530")
"Nayak, Rajendra" <rnayak@ti.com> writes:
> This series contains a set of patches which implement new 3430 errata, and some optimizations
> and fixes in the SR driver and DVFS path.
>
> These apply on the latest 'pm' branch and are validated on a 3430SDP platform.
Thanks, applying all but the scratchpad locking patch to PM branch.
See comment/question on that patch.
Kevin
next prev parent reply other threads:[~2009-06-04 23:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 12:43 [PATCH 00/06] OMAP3430 Errata, defect fixes and optimizations Nayak, Rajendra
2009-06-04 23:31 ` Kevin Hilman [this message]
2009-06-04 23:37 ` Kevin Hilman
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=87oct3d1ai.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.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