devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robherring2@gmail.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: devicetree-discuss@lists.ozlabs.org,
	Grant Likely <grant.likely@secretlab.ca>,
	Randy Dunlap <rdunlap@xenotime.net>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] devicetree: bindings: gpio-i2c belongs to i2c not gpio
Date: Mon, 11 Jun 2012 07:31:52 -0500	[thread overview]
Message-ID: <4FD5E538.4050601@gmail.com> (raw)
In-Reply-To: <20120611122648.GA4407@pengutronix.de>

On 06/11/2012 07:26 AM, Wolfram Sang wrote:
> On Fri, Apr 20, 2012 at 05:08:02PM +0200, Wolfram Sang wrote:
>> gpio-i2c describes an I2C controller (using gpios for data and clock),
>> so it must be described in i2c, not gpio.
>>
>> Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
>> ---
>>  .../{gpio/gpio_i2c.txt => i2c/gpio-i2c.txt}        |    0
>>  1 file changed, 0 insertions(+), 0 deletions(-)
>>  rename Documentation/devicetree/bindings/{gpio/gpio_i2c.txt => i2c/gpio-i2c.txt} (100%)
>>
>> diff --git a/Documentation/devicetree/bindings/gpio/gpio_i2c.txt b/Documentation/devicetree/bindings/i2c/gpio-i2c.txt
>> similarity index 100%
>> rename from Documentation/devicetree/bindings/gpio/gpio_i2c.txt
>> rename to Documentation/devicetree/bindings/i2c/gpio-i2c.txt
> 
> Any objections to me taking the patch via the i2c-tree?

That's fine.

Acked-by: Rob Herring <rob.herring@calxeda.com>

      reply	other threads:[~2012-06-11 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-20 15:08 [PATCH] devicetree: bindings: gpio-i2c belongs to i2c not gpio Wolfram Sang
2012-06-11 12:26 ` Wolfram Sang
2012-06-11 12:31   ` Rob Herring [this message]

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=4FD5E538.4050601@gmail.com \
    --to=robherring2@gmail.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=rdunlap@xenotime.net \
    --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;
as well as URLs for NNTP newsgroup(s).