All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Rajendra Nayak" <rnayak@ti.com>,
	linux-omap@vger.kernel.org, "Partha Basak" <p-basak2@ti.com>,
	"Benoît Cousson" <b-cousson@ti.com>
Subject: Re: [PATCH] OMAP: hwmod: Enable module wakeup if in smartidle
Date: Tue, 21 Sep 2010 14:03:59 -0700	[thread overview]
Message-ID: <871v8mizb4.fsf@deeprootsystems.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1009211425530.4677@utopia.booyaka.com> (Paul Walmsley's message of "Tue, 21 Sep 2010 14:27:09 -0600 (MDT)")

Paul Walmsley <paul@pwsan.com> writes:

> On Tue, 21 Sep 2010, Kevin Hilman wrote:
>
>> FWIW
>> 
>> Acked-by: Kevin Hilman <khilman@deeprootsystems.com>
>> 
>> as I'm using this for testing the various hwmod conversions.
>
> Thanks Kevin, added that in.  I know you've been testing some of the other 
> patches here too, so please let me know if you would like Tested-by:'s or 
> Acked-by:'s there.

I guess you can put a Tested-by for me on everything in your
hwmod_2.6.37 branch as I've been staging and testing those for a bit
now.

Also, one other thing I noticed in that branch: the locking patch from
me:

   OMAP: hwmod: separate list locking and hwmod hardware locking

has a stray '[PATCH]' in the shortlog which should probably be removed
as well.

Kevin

  reply	other threads:[~2010-09-21 21:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 14:28 [PATCH] OMAP: hwmod: Enable module wakeup if in smartidle Rajendra Nayak
2010-09-21 20:02 ` Paul Walmsley
2010-09-21 20:09   ` Kevin Hilman
2010-09-21 20:27     ` Paul Walmsley
2010-09-21 21:03       ` Kevin Hilman [this message]
2010-09-21 21:13         ` Paul Walmsley
2010-09-21 22:43           ` 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=871v8mizb4.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=b-cousson@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=p-basak2@ti.com \
    --cc=paul@pwsan.com \
    --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 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.