From: Vinod Koul <vkoul@kernel.org>
To: Claudiu Beznea <claudiu.beznea@microchip.com>
Cc: jckuo@nvidia.com, kishon@kernel.org, thierry.reding@gmail.com,
jonathanh@nvidia.com, nkristam@nvidia.com,
linux-phy@lists.infradead.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] phy: tegra: xusb: check return value of devm_kzalloc()
Date: Wed, 21 Jun 2023 23:07:23 +0530 [thread overview]
Message-ID: <ZJM1U9RPV4DUPgWp@matsya> (raw)
In-Reply-To: <20230531073950.145339-1-claudiu.beznea@microchip.com>
On 31-05-23, 10:39, Claudiu Beznea wrote:
> devm_kzalloc() returns a pointer to dynamically allocated memory.
> Pointer could be NULL in case allocation fails. Check pointer validity.
> Identified with coccinelle (kmerr.cocci script).
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2023-06-21 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 7:39 [PATCH] phy: tegra: xusb: check return value of devm_kzalloc() Claudiu Beznea
2023-06-01 9:39 ` Thierry Reding
2023-06-21 17:37 ` Vinod Koul [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=ZJM1U9RPV4DUPgWp@matsya \
--to=vkoul@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=jckuo@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nkristam@nvidia.com \
--cc=thierry.reding@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