From: Markus Elfring <Markus.Elfring@web.de>
To: Henry Martin <bsdhenrymartin@gmail.com>,
linux-aspeed@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Cc: LKML <linux-kernel@vger.kernel.org>,
"Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Arnd Bergmann" <arnd@arndb.de>,
"Bjorn Andersson" <andersson@kernel.org>,
"Herve Codina" <herve.codina@bootlin.com>,
"Joel Stanley" <joel@jms.id.au>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Subject: Re: [PATCH v3] drivers/misc: Add NULL check in aspeed_lpc_enable_snoop
Date: Tue, 1 Apr 2025 09:09:08 +0200 [thread overview]
Message-ID: <03d87a25-02ea-4e4a-8d3f-c2fcdc4d068e@web.de> (raw)
In-Reply-To: <20250401033935.17617-1-bsdhenrymartin@gmail.com>
> devm_kasprintf() return NULL if memory allocation fails. Currently,
…
call? failed?
> Add NULL check after devm_kasprintf() to prevent this issue.
Do you propose to improve this function implementation a bit more?
…
> ---
> V2 -> V3: Simplify the arrary access and correct commit message.
…
* Would you like to avoid a typo here?
* I imagine that there is a need to offer such adjustments
in separate update steps.
https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.14#n81
* Please choose a more appropriate subsystem specification.
https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/log/drivers/soc/aspeed/aspeed-lpc-snoop.c?h=next-20250331
* How do you think about to append parentheses to a function name
also in the summary phrase?
Regards,
Markus
next prev parent reply other threads:[~2025-04-01 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 3:39 [PATCH v3] drivers/misc: Add NULL check in aspeed_lpc_enable_snoop Henry Martin
2025-04-01 7:09 ` Markus Elfring [this message]
2025-04-01 7:37 ` [PATCH v4?] " Markus Elfring
-- strict thread matches above, loose matches on Subject: below --
2025-03-31 15:40 [PATCH v3] " Henry Martin
2025-03-31 16:15 ` Markus Elfring
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=03d87a25-02ea-4e4a-8d3f-c2fcdc4d068e@web.de \
--to=markus.elfring@web.de \
--cc=andersson@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=arnd@arndb.de \
--cc=bsdhenrymartin@gmail.com \
--cc=herve.codina@bootlin.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=u.kleine-koenig@baylibre.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