From: Rob Herring <robh@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
Javier Martinez Canillas <javier@dowhile0.org>,
David Lechner <david@lechnology.com>,
Divagar Mohandass <divagar.mohandass@intel.com>,
Peter Rosin <peda@axentia.se>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 3/4] dt-bindings: at24: extend the list of supported chips
Date: Tue, 2 Jan 2018 10:03:55 -0600 [thread overview]
Message-ID: <20180102160355.xllnymodcfccvia7@rob-hp-laptop> (raw)
In-Reply-To: <20171228104913.29873-4-brgl@bgdev.pl>
On Thu, Dec 28, 2017 at 11:49:12AM +0100, Bartosz Golaszewski wrote:
> Add other variants of at24 EEPROMs we support in the driver to the
> list of allowed compatible fallbacks.
>
> Signed-off-by: Bartosz Golaszewski <brgl@bgdev.pl>
> Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
> ---
> Documentation/devicetree/bindings/eeprom/at24.txt | 9 +++++++++
> 1 file changed, 9 insertions(+)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-01-02 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 10:49 [PATCH v4 0/4] eeprom: at24: device tree support fixes Bartosz Golaszewski
2017-12-28 10:49 ` [PATCH v4 1/4] dt-bindings: at24: consistently document the compatible property Bartosz Golaszewski
2017-12-28 11:57 ` Andy Shevchenko
2018-01-02 16:00 ` Rob Herring
2017-12-28 10:49 ` [PATCH v4 2/4] dt-bindings: at24: fix formatting and style Bartosz Golaszewski
2018-01-02 16:01 ` Rob Herring
2017-12-28 10:49 ` [PATCH v4 3/4] dt-bindings: at24: extend the list of supported chips Bartosz Golaszewski
2018-01-02 16:03 ` Rob Herring [this message]
2017-12-28 10:49 ` [PATCH v4 4/4] eeprom: at24: extend the list of chips supported in DT Bartosz Golaszewski
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=20180102160355.xllnymodcfccvia7@rob-hp-laptop \
--to=robh@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=divagar.mohandass@intel.com \
--cc=javier@dowhile0.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peda@axentia.se \
/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
all inboxes | Powered by JetHome®