From: Vladimir Zapolskiy <vz@mleia.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: GregKH <greg@kroah.com>,
srinivas.kandagatla@linaro.org, maxime.ripard@free-electrons.com,
wsa@the-dreams.de, broonie@kernel.org,
linux-kernel@vger.kernel.org, pantelis.antoniou@konsulko.com,
bgolaszewski@baylibre.com
Subject: Re: [PATCHv7 3/7] eeprom: at24: extend driver to plug into the NVMEM framework
Date: Thu, 3 Mar 2016 01:03:05 +0200 [thread overview]
Message-ID: <56D77129.6090100@mleia.com> (raw)
In-Reply-To: <20160302214859.GA15541@lunn.ch>
On 02.03.2016 23:48, Andrew Lunn wrote:
> On Wed, Mar 02, 2016 at 11:46:39PM +0200, Vladimir Zapolskiy wrote:
>> Hi Andrew,
>>
>> On 26.02.2016 21:59, Andrew Lunn wrote:
>>> Add a regmap for accessing the EEPROM, and then use that with the
>>> NVMEM framework. Set the NVMEM config structure to enable backward, so
>>> that the 'eeprom' file in sys is provided by the framework.
>>>
>>> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
>>> Acked-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
>>> Tested-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
>>> ---
>>
>> [snip]
>>
>>> +static int at24_regmap_read(void *context, const void *reg, size_t reg_size,
>>> + void *val, size_t val_size)
>>> +{
>>> + struct at24_data *at24 = context;
>>> + off_t offset = *(u32 *)reg;
>>> + int err;
>>> +
>>> + err = at24_read(at24, val, offset, val_size);
>>> + if (err)
>>> + return err;
>>> + return 0;
>>
>> return at24_read(at24, val, offset, val_size);
>>
>> Minus 5 LoC.
>
> And everything breaks :-(
>
> regmap expects either an error code, or 0. Return a positive value and
> it is not happy.
>
Well, do you agree that semantically my proposed change is equal to the
original one?
Let see...
static int at24_regmap_read() {
int err;
err = at24_read(at24, val, offset, val_size);
if (err)
return err;
return 0;
}
I don't see a check for (err <= 0) returned.
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2016-03-02 23:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 19:59 [PATCHv7 0/7] Convert exiting EEPROM drivers to NVMEM Andrew Lunn
2016-02-26 19:59 ` [PATCHv7 1/7] nvmem: Add flag to export NVMEM to root only Andrew Lunn
2016-02-26 19:59 ` [PATCHv7 2/7] nvmem: Add backwards compatibility support for older EEPROM drivers Andrew Lunn
2016-02-26 19:59 ` [PATCHv7 3/7] eeprom: at24: extend driver to plug into the NVMEM framework Andrew Lunn
2016-03-02 21:46 ` Vladimir Zapolskiy
2016-03-02 21:48 ` Andrew Lunn
2016-03-02 23:03 ` Vladimir Zapolskiy [this message]
2016-02-26 19:59 ` [PATCHv7 4/7] eeprom: at25: Remove in kernel API for accessing the EEPROM Andrew Lunn
2016-02-28 21:02 ` Wolfram Sang
2016-02-26 19:59 ` [PATCHv7 5/7] eeprom: at25: extend driver to plug into the NVMEM framework Andrew Lunn
2016-03-02 21:56 ` Vladimir Zapolskiy
2016-02-26 19:59 ` [PATCHv7 6/7] eeprom: 93xx46: " Andrew Lunn
2016-03-02 22:08 ` Vladimir Zapolskiy
2016-03-02 22:26 ` Andrew Lunn
2016-03-02 23:18 ` Vladimir Zapolskiy
2016-02-26 19:59 ` [PATCHv7 7/7] misc: at24: replace memory_accessor with nvmem_device_read Andrew Lunn
2016-02-28 21:01 ` Wolfram Sang
2016-03-02 0:56 ` [PATCHv7 0/7] Convert exiting EEPROM drivers to NVMEM Greg KH
2016-03-06 12:06 ` Wolfram Sang
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=56D77129.6090100@mleia.com \
--to=vz@mleia.com \
--cc=andrew@lunn.ch \
--cc=bgolaszewski@baylibre.com \
--cc=broonie@kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=srinivas.kandagatla@linaro.org \
--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