From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Christian Ruppert <christian.ruppert@abilis.com>,
Rob Herring <robherring2@gmail.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
<linux-i2c@vger.kernel.org>,
"Ben Dooks (embedded platforms)" <ben-linux@fluff.org>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Landley <rob@landley.net>,
<devicetree-discuss@lists.ozlabs.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Pierrick Hascoet <pierrick.hascoet@abilis.com>
Subject: Re: [PATCH v9] i2c-designware: make SDA hold time configurable
Date: Wed, 26 Jun 2013 09:53:36 +0530 [thread overview]
Message-ID: <51CA6CC8.6070305@synopsys.com> (raw)
In-Reply-To: <20130625163902.GA2973@katana>
On 06/25/2013 10:09 PM, Wolfram Sang wrote:
> Hi,
>
> On Fri, Jun 21, 2013 at 11:53:42AM +0200, Christian Ruppert wrote:
>> > This patch makes the SDA hold time configurable through device tree.
>> >
>> > Signed-off-by: Christian Ruppert <christian.ruppert@abilis.com>
>> > Signed-off-by: Pierrick Hascoet <pierrick.hascoet@abilis.com>
>> > ---
>> > .../devicetree/bindings/i2c/i2c-designware.txt | 14 ++++++++++++++
>> > arch/arc/boot/dts/abilis_tb100_dvk.dts | 10 +++++-----
>> > arch/arc/boot/dts/abilis_tb101_dvk.dts | 10 +++++-----
> Vineet, an ack for those would be nice since I think it is better if I
> take all this via I2C.
>
Certainly, I was waiting for you guys to converge :-)
Acked-by: Vineet Gupta <vgupta@synopsys.com> # for arch/arc/boot/dts/*
-Vineet
next prev parent reply other threads:[~2013-06-26 4:23 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130327084158.GB11010@ab42.lan>
[not found] ` <1364373760-12469-1-git-send-email-christian.ruppert@abilis.com>
2013-05-14 11:07 ` [PATCH v7] i2c-designware: make SDA hold time configurable Mika Westerberg
2013-05-14 13:04 ` [PATCH REBASE] " Christian Ruppert
2013-06-10 15:29 ` Wolfram Sang
2013-06-12 14:47 ` Christian Ruppert
2013-06-17 8:23 ` Mika Westerberg
2013-06-19 9:45 ` Wolfram Sang
2013-06-19 13:58 ` Christian Ruppert
2013-06-19 15:20 ` Wolfram Sang
2013-06-20 8:44 ` Christian Ruppert
2013-06-17 20:55 ` Rob Herring
2013-06-18 7:44 ` [PATCH v8] " Christian Ruppert
2013-06-20 20:04 ` Wolfram Sang
2013-06-20 20:37 ` Wolfram Sang
2013-06-21 9:53 ` [PATCH v9] " Christian Ruppert
2013-06-25 16:39 ` Wolfram Sang
2013-06-26 4:23 ` Vineet Gupta [this message]
2013-06-26 8:55 ` [PATCH v10] " Christian Ruppert
2013-06-26 8:57 ` Vineet Gupta
2013-06-26 14:07 ` Wolfram Sang
2013-07-03 11:43 ` Arnd Bergmann
2013-07-03 13:29 ` Christian Ruppert
2013-07-03 14:20 ` Arnd Bergmann
2013-07-03 14:38 ` Christian Ruppert
2013-07-03 14:42 ` Arnd Bergmann
2013-07-03 14:44 ` Arnd Bergmann
2013-07-03 14:59 ` Christian Ruppert
2013-07-03 15:07 ` Stehle Vincent-B46079
2013-07-03 15:26 ` Arnd Bergmann
2013-06-18 10:32 ` [PATCH REBASE] " Andy Shevchenko
2013-05-17 8:29 ` [PATCH v7] " Wolfram Sang
2013-05-17 8:44 ` Mika Westerberg
2013-05-17 8:56 ` Wolfram Sang
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=51CA6CC8.6070305@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=ben-linux@fluff.org \
--cc=christian.ruppert@abilis.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=pierrick.hascoet@abilis.com \
--cc=rob@landley.net \
--cc=robherring2@gmail.com \
--cc=wsa@the-dreams.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;
as well as URLs for NNTP newsgroup(s).