[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a5a7515e-a35c-46dd-8522-0daa41e23b1d@web.de>
Date: Wed, 15 Oct 2025 13:24:58 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Li Qiang <liqiang01@...inos.cn>, linux-wireless@...r.kernel.org,
brcm80211-dev-list.pdl@...adcom.com, brcm80211@...ts.linux.dev,
Arend van Spriel <arend.vanspriel@...adcom.com>
Cc: LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] wifi: brcmfmac: Add null pointer check to
brcmf_acpi_probe
> devm_kasprintf() returns a pointer to dynamically allocated memory
> which can be NULL upon failure.
Will another imperative wording approach become more helpful for an improved
change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.17#n94
Can a summary phrase like “Prevent null pointer dereference in brcmf_acpi_probe()”
be nicer?
Regards,
Markus
Powered by blists - more mailing lists