From: Wolfram Sang <wsa@the-dreams.de>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH] eeprom: at24: check at24_read/write arguments
Date: Sat, 2 Dec 2017 23:36:04 +0100 [thread overview]
Message-ID: <20171202223604.rd4i2e5rzkkzhsok@ninjato> (raw)
In-Reply-To: <e2b228a3-0dc9-3c47-91e0-e28d12f3da2d@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 172 bytes --]
For the record:
> Best solution would be if nvmem core guarantees that all calls to
> the nvmem provider read/write callbacks are done with valid
> parameters only.
+1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-02 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 6:47 [PATCH] eeprom: at24: check at24_read/write arguments Heiner Kallweit
2017-11-27 12:33 ` Bartosz Golaszewski
2017-11-27 19:40 ` Heiner Kallweit
2017-11-27 19:44 ` Bartosz Golaszewski
2017-12-02 22:36 ` Wolfram Sang [this message]
2017-11-29 14:58 ` 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=20171202223604.rd4i2e5rzkkzhsok@ninjato \
--to=wsa@the-dreams.de \
--cc=brgl@bgdev.pl \
--cc=hkallweit1@gmail.com \
--cc=linux-i2c@vger.kernel.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).