mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Gaosheng Cui <cuigaosheng1@huawei.com>, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, wangweiyang2@huawei.com
Subject: Re: [PATCH -next 0/2] A few fixup patches for nvmem
Date: Wed, 17 Aug 2022 09:53:20 +0100	[thread overview]
Message-ID: <c798c5fd-e877-9f70-8733-26d1d494a637@linaro.org> (raw)
In-Reply-To: <20220816134935.263825-1-cuigaosheng1@huawei.com>



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(-)
> 

  parent reply	other threads:[~2022-08-17  8:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 13:49 Gaosheng Cui
2022-08-16 13:49 ` [PATCH -next 1/2] nvmem: core: Fix memleak in nvmem_register() Gaosheng Cui
2022-08-16 13:49 ` [PATCH -next 2/2] nvmem: core: add error handling for dev_set_name Gaosheng Cui
2022-08-17  8:53 ` Srinivas Kandagatla [this message]
2022-08-17  9:08   ` [PATCH -next 0/2] A few fixup patches for nvmem cuigaosheng

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=c798c5fd-e877-9f70-8733-26d1d494a637@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=cuigaosheng1@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wangweiyang2@huawei.com \
    /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
all inboxes | Powered by JetHome®