From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Wolfram Sang <w.sang@pengutronix.de>,
"khali@linux-fr.org" <khali@linux-fr.org>,
"ben-linux@fluff.org" <ben-linux@fluff.org>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH V1] i2c: gpio: Use open drain support from gpio driver
Date: Wed, 7 Mar 2012 23:38:25 +0530 [thread overview]
Message-ID: <4F57A419.9090501@nvidia.com> (raw)
In-Reply-To: <20120307174443.GV3107@opensource.wolfsonmicro.com>
The open drain support is already available from next-20120306.
I was waiting for the change to be in tree before sending this patch.
Hope I am not missing anything here.
On Wednesday 07 March 2012 11:14 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Wed, Mar 07, 2012 at 06:39:22PM +0100, Wolfram Sang wrote:
>> On Wed, Mar 07, 2012 at 05:31:57PM +0000, Mark Brown wrote:
>>> Reviwed-by: Mark Brown<broonie@opensource.wolfsonmicro.com>
>> Typo ;)
> Not at all, it's a direct demonstration of the quick review I did! :P
>
> * Unknown Key
> * 0x6E30FDDD
next prev parent reply other threads:[~2012-03-07 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 13:38 [PATCH V1] i2c: gpio: Use open drain support from gpio driver Laxman Dewangan
2012-03-07 17:31 ` Mark Brown
2012-03-07 17:39 ` Wolfram Sang
2012-03-07 17:44 ` Mark Brown
2012-03-07 18:08 ` Laxman Dewangan [this message]
2012-03-07 19:17 ` Mark Brown
2012-03-08 6:24 ` Linus Walleij
2012-03-08 7:41 ` Wolfram Sang
2012-03-08 8:59 ` Linus Walleij
2012-03-08 11:01 ` Mark Brown
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=4F57A419.9090501@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=khali@linux-fr.org \
--cc=linus.walleij@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=w.sang@pengutronix.de \
/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