From: Rob Herring <robh@kernel.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: devicetree@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-sh@vger.kernel.org, Simon Horman <horms@verge.net.au>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: move I2C eeprom descriptions to the proper file
Date: Thu, 7 Jan 2016 17:00:12 -0600 [thread overview]
Message-ID: <20160107230012.GA15023@rob-hp-laptop> (raw)
In-Reply-To: <1452199860-3601-2-git-send-email-wsa@the-dreams.de>
On Thu, Jan 07, 2016 at 09:50:59PM +0100, Wolfram Sang wrote:
> From: Wolfram Sang <wsa+renesas@sang-engineering.com>
>
> EEPROMs can have additional properties, so they are not suitable for
> trivial-devices.txt. Move most bindings to the designated eeprom.txt.
> Add the missing "atmel,24c08" while doing that. Note that the remaining
> ones in trivial-devices need to be dealt with seperately because of
s/seperately/separately/
> improper manufacturer names.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> Documentation/devicetree/bindings/eeprom/eeprom.txt | 19 ++++++++++++++-----
> .../devicetree/bindings/i2c/trivial-devices.txt | 13 -------------
> 2 files changed, 14 insertions(+), 18 deletions(-)
Acked-by: Rob Herring <robh@kernel.org>
Fine to take these thru your tree.
Rob
next prev parent reply other threads:[~2016-01-07 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 20:50 [PATCH 0/2] dt-bindings: refactor i2c eeprom bindings, step 1 Wolfram Sang
2016-01-07 20:50 ` [PATCH 1/2] dt-bindings: move I2C eeprom descriptions to the proper file Wolfram Sang
2016-01-07 23:00 ` Rob Herring [this message]
2016-01-10 8:40 ` Wolfram Sang
2016-01-07 20:51 ` [PATCH 2/2] dt-bindings: i2c: eeprom: add another EEPROM device Wolfram Sang
2016-01-07 23:01 ` 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=20160107230012.GA15023@rob-hp-laptop \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--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