From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wolfram Sang Subject: Re: [PATCH] eeprom: at24: check at24_read/write arguments Date: Sat, 2 Dec 2017 23:36:04 +0100 Message-ID: <20171202223604.rd4i2e5rzkkzhsok@ninjato> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3chydlpsad2shiz2" Return-path: Received: from sauhun.de ([88.99.104.3]:38642 "EHLO pokefinder.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751996AbdLBWgG (ORCPT ); Sat, 2 Dec 2017 17:36:06 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-i2c-owner@vger.kernel.org List-Id: linux-i2c@vger.kernel.org To: Heiner Kallweit Cc: Bartosz Golaszewski , "linux-i2c@vger.kernel.org" --3chydlpsad2shiz2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 --3chydlpsad2shiz2 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAlojKtAACgkQFA3kzBSg Kbb44RAAtWtuixzE4o95D/hQnfqYjbfC5tfEFSYnYQxYcVlxnffqLt0CJuFYVRd5 5maUjCzdiIyohPhUa2zj+KrGu1mjTTFIGPG1d6aoqwHzAaxjfqfLD2y5FWb1qu3y OlSJN/0Twtsi7OurQG79UCLHy9qs0/kbQ1x4EtfVd/N1pROZ1CqMjJO/YpLAdD6C RbYXvyHDewWLQt6xDlUma142D9K5cq87bWRfQOtXDtIZQkwqi8GAcsb4PdrsSakD abCvlBOd51TWwWYn8SYbZXXKUZ0lQ5LsgLDrrKwDd869/0VoWV8FcTkaCB4zxqXl fhBHa4H1FU4HG+oBzlLl1NJeAfU1FwpiLF3QoGdiWVN8d2g02WQHdW/iT8iFU80L QGHw5YRSjVfwOk7FdZ37cARqhSRs58vloDu++SiL7/aLeTieSIPHEl2Ehm/YuMpz bWYnhx6C5P9BZklAeYqNiauPehFqE24JiIqmE7KgHIY3nInzs5bFtDEY8C+do0ji HECSY/4HtsRd9Rw3DSfyV5vRLRo55BcxdJo8mcWF/hkQQtZuNkas/NeGQMyAQ6HH AjsllirzTZie7koM1RhaNqDCEcGORGQ2kp6ByiNExZlLvYgflrnXGIzb0ueukEzB LG1+lTju06651EOIz0EquoPuuQGNMpujgPLeFuusJlXEBV5oXpg= =+5p+ -----END PGP SIGNATURE----- --3chydlpsad2shiz2--