From: alanx.chiang@intel.com
To: linux-i2c@vger.kernel.org
Cc: andy.yeh@intel.com, sakari.ailus@linux.intel.com,
andriy.shevchenko@linux.intel.com, andriy.shevchenko@intel.com,
rajmohan.mani@intel.com, andy.shevchenko@gmail.com,
tfiga@chromium.org, jcliang@chromium.org, brgl@bgdev.pl,
robh+dt@kernel.org, mark.rutland@arm.com, arnd@arndb.de,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Alan Chiang <alanx.chiang@intel.com>
Subject: [RESEND PATCH v4 0/2] Add a property in at24.c
Date: Mon, 2 Jul 2018 17:12:18 +0800 [thread overview]
Message-ID: <1530522740-2798-1-git-send-email-alanx.chiang@intel.com> (raw)
From: Alan Chiang <alanx.chiang@intel.com>
This RESEND PATCH only adds the Acked-by and Reviewed-by,
no other patch for the codes.
In at24.c, it uses 8-bit addressing by default. In this patch,
add a property address-width that provides a flexible method to
pass the information to the driver.
Alan Chiang (2):
dt-bindings: at24: Add address-width property
eeprom: at24: Add support for address-width property
Documentation/devicetree/bindings/eeprom/at24.txt | 2 ++
drivers/misc/eeprom/at24.c | 17 +++++++++++++++++
2 files changed, 19 insertions(+)
--
2.7.4
next reply other threads:[~2018-07-02 9:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 9:12 alanx.chiang [this message]
2018-07-02 9:12 ` [RESEND PATCH v4 1/2] dt-bindings: at24: Add address-width property alanx.chiang
2018-07-05 21:22 ` Rob Herring
2018-07-05 20:24 ` Robert P. J. Day
2018-07-09 3:12 ` Chiang, AlanX
2018-07-09 8:52 ` Bartosz Golaszewski
2018-07-17 8:01 ` Bartosz Golaszewski
2018-07-24 11:07 ` sakari.ailus
2018-07-24 14:10 ` Bartosz Golaszewski
2018-07-02 9:12 ` [RESEND PATCH v4 2/2] eeprom: at24: Add support for " alanx.chiang
2018-07-02 11:59 ` [RESEND PATCH v4 0/2] Add a property in at24.c 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=1530522740-2798-1-git-send-email-alanx.chiang@intel.com \
--to=alanx.chiang@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy.yeh@intel.com \
--cc=arnd@arndb.de \
--cc=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jcliang@chromium.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rajmohan.mani@intel.com \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@chromium.org \
/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).