From: Rob Herring <robh+dt@kernel.org>
To: Divagar Mohandass <divagar.mohandass@intel.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
"wsa@the-dreams.de" <wsa@the-dreams.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Rajmohan Mani <rajmohan.mani@intel.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: add eeprom "size" property
Date: Tue, 15 Aug 2017 14:13:37 -0500 [thread overview]
Message-ID: <CAL_JsqLwUOY87ZuJGzeRa_vbUvBbFTfBgob4y2zG0ffnfSGbRQ@mail.gmail.com> (raw)
In-Reply-To: <1502736119-32084-2-git-send-email-divagar.mohandass@intel.com>
On Mon, Aug 14, 2017 at 1:41 PM, Divagar Mohandass
<divagar.mohandass@intel.com> wrote:
> This adds eeprom "size" as optional property for i2c eeproms.
>
> "size" should be mentioned in byte and it should refer
> to the eeprom size. This will be read by the driver and
> used to calculating the number of bytes in read/write calls.
>
> Signed-off-by: Divagar Mohandass <divagar.mohandass@intel.com>
> ---
> Documentation/devicetree/bindings/eeprom/eeprom.txt | 2 ++
> 1 file changed, 2 insertions(+)
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2017-08-15 19:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 18:41 [PATCH v2 0/3] enable eeprom "size" property and runtime pm Divagar Mohandass
2017-08-14 18:41 ` [PATCH v2 1/3] dt-bindings: add eeprom "size" property Divagar Mohandass
2017-08-15 19:13 ` Rob Herring [this message]
2017-08-22 9:11 ` Sakari Ailus
[not found] ` <20170822091107.uubxhwilkutduou7-S+BSfZ9RZZmRSg0ZkenSGLdO1Tsj/99ntUK59QYPAWc@public.gmane.org>
2017-08-30 3:57 ` Mohandass, Divagar
2017-08-14 18:41 ` [PATCH v2 2/3] eeprom: at24: add support to fetch eeprom device property "size" Divagar Mohandass
2017-08-22 9:13 ` Sakari Ailus
2017-08-30 3:57 ` Mohandass, Divagar
2017-08-14 18:41 ` [PATCH v2 3/3] eeprom: at24: enable runtime pm support Divagar Mohandass
2017-08-22 8:55 ` Sakari Ailus
[not found] ` <20170822085555.o4tqwxpa5ukgwet5-S+BSfZ9RZZmRSg0ZkenSGLdO1Tsj/99ntUK59QYPAWc@public.gmane.org>
2017-08-30 4:05 ` Mohandass, Divagar
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=CAL_JsqLwUOY87ZuJGzeRa_vbUvBbFTfBgob4y2zG0ffnfSGbRQ@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=divagar.mohandass@intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rajmohan.mani@intel.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).