From: Greg KH <gregkh@linuxfoundation.org>
To: void0red <void0red@gmail.com>
Cc: mudongliangabcd@gmail.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] usb: gadget: udc: replace kzalloc with devm_kzalloc in mv_udc_probe and add a check for this allocation.
Date: Fri, 24 Feb 2023 17:33:35 +0100 [thread overview]
Message-ID: <Y/jm3yk4oiFQLhNq@kroah.com> (raw)
In-Reply-To: <20230224143148.60-1-void0red@gmail.com>
On Fri, Feb 24, 2023 at 10:31:48PM +0800, void0red wrote:
> From: Kang Chen <void0red@gmail.com>
>
> This driver uses the unified memory management api, so replace
> kzalloc with devm_kzalloc to avoid a memory leak and add a check
> for this allocation.
>
> Reported-by: eriri <1527030098@qq.com>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=217081
>
> Signed-off-by: Kang Chen <void0red@gmail.com>
> ---
> v2 -> v1: replace kzalloc with devm_kzalloc
I see 2 v2 patches on the mailing list, how am I supposed to know which
one is correct?
Please fix up and resend a v3.
thanks,
greg k-h
prev parent reply other threads:[~2023-02-24 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 9:20 [PATCH] usb: gadget: udc: add return value check of kzalloc in mv_udc_probe void0red
2023-02-24 11:03 ` Dongliang Mu
2023-02-24 12:43 ` Kang Chen
2023-02-24 13:02 ` [PATCH] usb: gadget: udc: replace kzalloc with devm_kzalloc in mv_udc_probe and add a check for this allocation void0red
2023-02-24 13:13 ` Greg KH
2023-02-24 13:14 ` Dongliang Mu
2023-02-24 14:11 ` [PATCH v2] " void0red
2023-02-24 14:19 ` Greg KH
2023-02-24 17:01 ` Sergei Shtylyov
2023-02-25 4:11 ` [PATCH v3 1/2] usb: gadget: udc: add return value check of kzalloc in mv_udc_probe void0red
2023-02-25 4:11 ` [PATCH v3 2/2] usb: gadget: udc: replace kzalloc with devm_kzalloc " void0red
2023-02-24 14:31 ` [PATCH v2] usb: gadget: udc: replace kzalloc with devm_kzalloc in mv_udc_probe and add a check for this allocation void0red
2023-02-24 16:33 ` Greg KH [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=Y/jm3yk4oiFQLhNq@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mudongliangabcd@gmail.com \
--cc=void0red@gmail.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;
as well as URLs for NNTP newsgroup(s).