From: Nishanth Menon <nm@ti.com>
To: Kevin Hilman <khilman@ti.com>
Cc: Shweta Gulati <shweta.gulati@ti.com>,
linux-omap@vger.kernel.org, Thara Gopinath <thara@ti.com>,
Sanjeev Premi <premi@ti.com>
Subject: Re: [PATCH V4] OMAP3: PM: Set/clear T2 bit for Smartreflex on TWL
Date: Tue, 15 Feb 2011 08:48:34 +0530 [thread overview]
Message-ID: <4D59F08A.7080907@ti.com> (raw)
In-Reply-To: <87y65iz22v.fsf@ti.com>
Kevin Hilman wrote, on 02/15/2011 03:54 AM:
> "Menon, Nishanth"<nm@ti.com> writes:
>
>> On Fri, Feb 4, 2011 at 11:17, Shweta Gulati<shweta.gulati@ti.com> wrote:
>>> From: Thara Gopinath<thara@ti.com>
>>>
>> Gentle ping - folks after 8 days no comments, does this rev address
>> all previous comments? if so, it might be good to get some acks ;)
>
> Gentle reminder. Patchwork[1] keeps a queue of patches pending
> review/merge etc. If it's in patchwork it will get reviewed, most
> likely in the order it was received.
>
> There are lots of going on recently, so we have a good sized queue in
> patchwork.
Ofcourse, the intent of the ping here was for other reviewers of patches
from v2/v3 of this patch to provide their inputs so that we can move
this forward. Btw, other than maintainer, I am not completely sure if
ML based reviewers review based on patchworks sequencing ;).
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2011-02-15 3:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 5:47 [PATCH V4] OMAP3: PM: Set/clear T2 bit for Smartreflex on TWL Shweta Gulati
2011-02-12 10:40 ` Menon, Nishanth
2011-02-14 22:24 ` Kevin Hilman
2011-02-15 3:18 ` Nishanth Menon [this message]
2011-02-14 22:24 ` Kevin Hilman
2011-02-14 22:26 ` Kevin Hilman
2011-02-14 22:30 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2011-02-15 7:58 Shweta Gulati
2011-02-15 7:58 ` Shweta Gulati
2011-02-15 15:16 ` Jarkko Nikula
2011-02-15 15:16 ` Jarkko Nikula
2011-02-15 15:29 ` Jarkko Nikula
2011-02-15 15:29 ` Jarkko Nikula
2011-02-16 5:52 ` Gulati, Shweta
2011-02-16 5:52 ` Gulati, Shweta
2011-02-16 11:45 ` Jarkko Nikula
2011-02-16 11:45 ` Jarkko Nikula
2011-02-16 11:54 ` Gulati, Shweta
2011-02-16 11:54 ` Gulati, Shweta
2011-02-16 12:31 ` Jarkko Nikula
2011-02-16 12:31 ` Jarkko Nikula
2011-02-16 12:47 ` Gulati, Shweta
2011-02-16 12:47 ` Gulati, Shweta
2011-02-15 16:30 ` Vishwanath Sripathy
2011-02-15 16:30 ` Vishwanath Sripathy
2011-02-16 5:44 ` Gulati, Shweta
2011-02-16 5:44 ` Gulati, Shweta
2011-03-03 0:31 ` Kevin Hilman
2011-03-03 0:31 ` 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=4D59F08A.7080907@ti.com \
--to=nm@ti.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@ti.com \
--cc=shweta.gulati@ti.com \
--cc=thara@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.