From: Vivek Gautam <vivek.gautam@codeaurora.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
Stephen Boyd <sboyd@codeaurora.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] nvmem: core: Allow ignoring length when reading a cell
Date: Thu, 5 Jan 2017 15:16:16 +0530 [thread overview]
Message-ID: <6f65b752-a8c4-8c1c-fc8e-442ccb4af9e6@codeaurora.org> (raw)
In-Reply-To: <a5601dcd-8a32-0e99-5757-016049013001@linaro.org>
On 01/05/2017 03:10 PM, Srinivas Kandagatla wrote:
>
>
> On 05/01/17 05:34, Vivek Gautam wrote:
>> Hi Srinivas,
>>
>> On Tue, Dec 20, 2016 at 3:17 AM, Stephen Boyd <sboyd@codeaurora.org>
>> wrote:
>>> On 12/19, Vivek Gautam wrote:
>>>> nvmem_cell_read() API fills in the argument 'len' with
>>>> the number of bytes read from the cell. Many users don't
>>>> care about this length value. So allow users to pass a
>>>> NULL pointer to this len field.
>>>>
>>>> Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
>>>> ---
>>>
>>> Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
>>
>> Can you please pick this patch as well, adding Stephen's
>> 'Reviewed-by' tag.
>>
> This is already in my queue for 4.11 release, as this is an
> enhancement. I will send them to Greg once we hit rc4 or rc5.
Okay. Thanks for picking.
Regards
Vivek
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-01-05 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 6:53 [PATCH] nvmem: core: Allow ignoring length when reading a cell Vivek Gautam
2016-12-19 21:47 ` Stephen Boyd
2016-12-20 4:03 ` Vivek Gautam
2017-01-05 5:34 ` Vivek Gautam
2017-01-05 9:40 ` Srinivas Kandagatla
2017-01-05 9:46 ` Vivek Gautam [this message]
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=6f65b752-a8c4-8c1c-fc8e-442ccb4af9e6@codeaurora.org \
--to=vivek.gautam@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=sboyd@codeaurora.org \
--cc=srinivas.kandagatla@linaro.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).