Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Subject: Re: [PATCH -next 0/2] A few fixup patches for nvmem
To:     Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
        <gregkh@linuxfoundation.org>
CC:     <linux-kernel@vger.kernel.org>, <wangweiyang2@huawei.com>
References: <20220816134935.263825-1-cuigaosheng1@huawei.com>
 <c798c5fd-e877-9f70-8733-26d1d494a637@linaro.org>
From:   cuigaosheng <cuigaosheng1@huawei.com>
Message-ID: <a6511232-b08d-6e44-04f7-d67f1c11b003@huawei.com>
Date:   Wed, 17 Aug 2022 17:08:29 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <c798c5fd-e877-9f70-8733-26d1d494a637@linaro.org>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk

I'll take a closer look at this link, thank you very much!

Gaosheng

在 2022/8/17 16:53, Srinivas Kandagatla 写道:
>
>
> On 16/08/2022 14:49, Gaosheng Cui wrote:
>> This series contains a fixup patches to fix possible memleak,
>> and add error handling of dev_set_name to keep nvmem code
>> implementation consistent, in addition, it can also avoid
>> the possibility illegal address access. Thanks!
>>
>> Gaosheng Cui (2):
>>    nvmem: core: Fix memleak in nvmem_register()
>>    nvmem: core: add error handling for dev_set_name
>>
>
> I have applied these patches for now but remember the subject line 
> does not reflect the patch version or the cover letter does not 
> include any changes done over the versions.
>
> Please take a look at 
> https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html
>
>
> thanks,
> Srini
>
>>   drivers/nvmem/core.c | 27 +++++++++++++++------------
>>   1 file changed, 15 insertions(+), 12 deletions(-)
>>
> .