From: Baolin Wang <baolin.wang@linaro.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mark Brown <broonie@kernel.org>,
freeman.liu@spreadtrum.com, DTML <devicetree@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] nvmem: Add Spreadtrum SC27XX efuse support
Date: Mon, 9 Jul 2018 18:30:35 +0800 [thread overview]
Message-ID: <CAMz4kuKBxxJwbezu6RY23HBQG7jBCFPPVvb5nAkYnKZTT=r44w@mail.gmail.com> (raw)
In-Reply-To: <068e3671-2624-7e16-7387-185e688cb6ed@linaro.org>
On 9 July 2018 at 17:41, Srinivas Kandagatla
<srinivas.kandagatla@linaro.org> wrote:
>
>
> On 09/07/18 10:26, Baolin Wang wrote:
>>
>> Hi Srinivas,
>>
>> On 25 June 2018 at 14:31, Baolin Wang<baolin.wang@linaro.org> wrote:
>>>
>>> From: Freeman Liu<freeman.liu@spreadtrum.com>
>>>
>>> This patch add the efuse driver which is embeded in Spreadtrum SC27XX
>>> series PMICs. The sc27xx efuse contains 32 blocks and each block's
>>> data width is 16 bits.
>>>
>>> Signed-off-by: Freeman Liu<freeman.liu@spreadtrum.com>
>>> Signed-off-by: Baolin Wang<baolin.wang@linaro.org>
>>> ---
>>> Changes since v1:
>>> - Fix one typo.
>>> ---
>>
>> Do you have any comments for this patch set? Thanks.
>
> Thanks for your patience!
>
> These patches look good!, Normally I tend to send nvmem patches to Greg K.H
> just before rc5! I will queue them by end of this week!
Thanks.
--
Baolin Wang
Best Regards
prev parent reply other threads:[~2018-07-09 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 6:31 [PATCH v2 1/2] dt-bindings: nvmem: Add Spreadtrum SC27XX efuse controller documentation Baolin Wang
2018-06-25 6:31 ` [PATCH v2 2/2] nvmem: Add Spreadtrum SC27XX efuse support Baolin Wang
2018-07-09 9:26 ` Baolin Wang
2018-07-09 9:41 ` Srinivas Kandagatla
2018-07-09 10:30 ` Baolin Wang [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='CAMz4kuKBxxJwbezu6RY23HBQG7jBCFPPVvb5nAkYnKZTT=r44w@mail.gmail.com' \
--to=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=freeman.liu@spreadtrum.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).