From: Vivek Gautam <vivek.gautam@codeaurora.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: srinivas.kandagatla@linaro.org, maxime.ripard@free-electrons.com,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 2/2] nvmem: core: Allow getting nvmem cell with a NULL cell id
Date: Tue, 10 Jan 2017 13:29:53 +0530 [thread overview]
Message-ID: <92d78c9c-bb64-76b8-a0b6-07b3d730fb3f@codeaurora.org> (raw)
In-Reply-To: <20170109195341.GQ17126@codeaurora.org>
Hi
On 01/10/2017 01:23 AM, Stephen Boyd wrote:
> On 01/06, Vivek Gautam wrote:
>> The nvmem cell with a NULL cell name/id should be the one
>> with no accompanying 'nvmem-cell-names' property, and thus
>> will be the cell at index 0 in the device tree.
>> So, we default to index 0 and update the cell index only when
>> nvmem cell name id exists.
>>
>> Suggested-by: Stephen Boyd <sboyd@codeaurora.org>
>> Signed-off-by: Vivek Gautam <vivek.gautam@codeaurora.org>
> Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
>
> Except the typo below:
Thanks. Have fixed the typo in v2 version of the patch.
Regards
Vivek
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-01-10 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 9:10 [PATCH 1/2] nvmem: core: Correct a bunch of function documentations Vivek Gautam
2017-01-06 9:10 ` [PATCH 2/2] nvmem: core: Allow getting nvmem cell with a NULL cell id Vivek Gautam
2017-01-09 19:53 ` Stephen Boyd
2017-01-10 7:59 ` Vivek Gautam [this message]
2017-01-09 19:52 ` [PATCH 1/2] nvmem: core: Correct a bunch of function documentations Stephen Boyd
2017-01-10 7:58 ` Vivek Gautam
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=92d78c9c-bb64-76b8-a0b6-07b3d730fb3f@codeaurora.org \
--to=vivek.gautam@codeaurora.org \
--cc=linux-arm-msm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.