From: Kevin Hilman <khilman@ti.com>
To: Ben Dooks <ben-i2c@fluff.org>
Cc: Shubhrajyoti D <shubhrajyoti@ti.com>,
linux-i2c@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH][RFC] OMAP4: I2C : I2C context save
Date: Wed, 13 Jul 2011 14:15:19 -0700 [thread overview]
Message-ID: <87k4blopaw.fsf@ti.com> (raw)
In-Reply-To: <20110713190723.GA3369@freya.fluff.org> (Ben Dooks's message of "Wed, 13 Jul 2011 20:07:23 +0100")
Ben Dooks <ben-i2c@fluff.org> writes:
> On Tue, Jul 05, 2011 at 02:50:46PM +0530, Shubhrajyoti D wrote:
>> Currently the OMAP4 doesnot hit device off still the
>> driver may have support for it.Adding support for the
>> same.
>>
>> Signed-off-by: Shubhrajyoti D <shubhrajyoti@ti.com>
>
> I guess since the previous set has been taken by Kevin
> then these will be too.
Sure, I'll pick these up, but it's probably to late for v3.1.
We've already submitted the bulk of the OMAP stuff for v3.1.
Kevin
next prev parent reply other threads:[~2011-07-13 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 9:20 [PATCH][RFC] OMAP4: I2C : I2C context save Shubhrajyoti D
[not found] ` <1309857646-29401-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2011-07-13 19:07 ` Ben Dooks
2011-07-13 21:15 ` Kevin Hilman [this message]
[not found] ` <87k4blopaw.fsf-l0cyMroinI0@public.gmane.org>
2011-07-13 21:27 ` Hilman, Kevin
2011-07-14 10:53 ` Shubhrajyoti
[not found] ` <4E1ECABA.7010306-l0cyMroinI0@public.gmane.org>
2011-07-14 15:38 ` Kevin Hilman
[not found] <1308559552-24028-1-git-send-email-shubhrajyoti@ti.com>
[not found] ` <87ips08qis.fsf@ti.com>
[not found] ` <87ips08qis.fsf-l0cyMroinI0@public.gmane.org>
2011-06-20 15:43 ` Shubhrajyoti
[not found] ` <4DFF6A9E.5050209-l0cyMroinI0@public.gmane.org>
2011-07-05 18:31 ` Kevin Hilman
[not found] ` <87y60cr344.fsf-l0cyMroinI0@public.gmane.org>
2011-07-06 6:21 ` Shubhrajyoti
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=87k4blopaw.fsf@ti.com \
--to=khilman@ti.com \
--cc=ben-i2c@fluff.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=shubhrajyoti@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