From: Wolfram Sang <w.sang@pengutronix.de>
To: devicetree-discuss@lists.ozlabs.org
Cc: Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
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 14:26:48 +0200 [thread overview]
Message-ID: <20120611122648.GA4407@pengutronix.de> (raw)
In-Reply-To: <1334934487-19201-1-git-send-email-w.sang@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
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?
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-06-11 12:26 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 [this message]
2012-06-11 12:31 ` Rob Herring
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=20120611122648.GA4407@pengutronix.de \
--to=w.sang@pengutronix.de \
--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=rob.herring@calxeda.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;
as well as URLs for NNTP newsgroup(s).