From: Sven Van Asbroeck <svendev@arcx.com>
To: svendev@arcx.com, robh+dt@kernel.org, mark.rutland@arm.com,
wsa@the-dreams.de, brgl@bgdev.pl, nsekhar@ti.com,
sakari.ailus@linux.intel.com, david@lechnology.com,
javier@dowhile0.org, divagar.mohandass@intel.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: [PATCH v5 0/2] at24: support eeproms that do not auto-rollover reads.
Date: Thu, 7 Dec 2017 09:36:16 -0500 [thread overview]
Message-ID: <1512657378-5221-1-git-send-email-svendev@arcx.com> (raw)
v5:
at Rob Herring's request, renamed devicetree property:
at24,no-read-rollover -> no-read-rollover
v4:
renamed devicetree property:
no-read-rollover -> at24,no-read-rollover
dt-bindings update now a separate patch
v3:
rebased against at24 maintainer's devel staging branch:
git://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git at24/devel
clarified some of the comments and wording
v2:
kbuild test robot feedback: correct
"warning: comparison of distinct pointer types lacks a cast"
build warning on some compilers / architectures.
v1:
original patch
Sven Van Asbroeck (2):
at24: support eeproms that do not auto-rollover reads.
dt-bindings: add eeprom "at24,no-read-rollover" property
.../devicetree/bindings/eeprom/eeprom.txt | 5 +++
drivers/misc/eeprom/at24.c | 37 +++++++++++++++-------
include/linux/platform_data/at24.h | 2 ++
3 files changed, 32 insertions(+), 12 deletions(-)
--
1.9.1
next reply other threads:[~2017-12-07 14:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 14:36 Sven Van Asbroeck [this message]
2017-12-07 14:36 ` [PATCH v5 1/2] at24: support eeproms that do not auto-rollover reads Sven Van Asbroeck
[not found] ` <1512657378-5221-2-git-send-email-svendev-fuHqz3Nb1YI@public.gmane.org>
2017-12-07 16:26 ` Bartosz Golaszewski
[not found] ` <CAMRc=MdhJRD+G18Xh5vfmaHHdJ+g9EnDTxUHVxhzDzVt-D0KMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-07 19:02 ` Uwe Kleine-König
2017-12-07 21:33 ` Bartosz Golaszewski
[not found] ` <CAMRc=MeEnDYjDTpE=XKuP3LricsnEnh0RHKMzxEPUcOS6E0tPQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-07 21:57 ` Uwe Kleine-König
2017-12-07 14:36 ` [PATCH v5 2/2] dt-bindings: add eeprom "no-read-rollover" property Sven Van Asbroeck
2017-12-07 15:40 ` 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=1512657378-5221-1-git-send-email-svendev@arcx.com \
--to=svendev@arcx.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=nsekhar@ti.com \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.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).