[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024100608-chomp-undiluted-c3e2@gregkh>
Date: Sun, 6 Oct 2024 12:08:16 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Markus Elfring <Markus.Elfring@....de>
Cc: Zichen Xie <zichenxie0106@...il.com>, alsa-devel@...a-project.org,
linux-sound@...r.kernel.org, linux-arm-msm@...r.kernel.org,
Jaroslav Kysela <perex@...ex.cz>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Rohit kumar <quic_rohkumar@...cinc.com>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Takashi Iwai <tiwai@...e.com>, stable@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Chenyuan Yang <chenyuan0y@...il.com>,
Zijie Zhao <zzjas98@...il.com>
Subject: Re: [PATCH] ASoC: qcom: Fix NULL Dereference in
asoc_qcom_lpass_cpu_platform_probe()
On Sun, Oct 06, 2024 at 10:56:51AM +0200, Markus Elfring wrote:
> >>> A devm_kzalloc() in asoc_qcom_lpass_cpu_platform_probe() could
> >>
> >> call?
> >>
> >>
> >>> possibly return NULL pointer. NULL Pointer Dereference may be
> >>> triggerred without addtional check.
> >> …
> >>
> >> * How do you think about to use the term “null pointer dereference”
> >> for the final commit message (including the summary phrase)?
> >>
> >> * Would you like to avoid any typos here?
> >>
> >>
> >> …
> >>> ---
> >>> sound/soc/qcom/lpass-cpu.c | 2 ++
> >>
> >> Did you overlook to add a version description behind the marker line?
> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.12-rc1#n723
> …
> > This is the semi-friendly patch-bot of Greg Kroah-Hartman.
> >
> > Markus, you seem to have sent a nonsensical or otherwise pointless
> > review comment to a patch submission on a Linux kernel developer mailing
> > list. I strongly suggest that you not do this anymore. Please do not
> > bother developers who are actively working to produce patches and
> > features with comments that, in the end, are a waste of time.
> >
> > Patch submitter, please ignore Markus's suggestion; you do not need to
> > follow it at all. The person/bot/AI that sent it is being ignored by
> > almost all Linux kernel maintainers for having a persistent pattern of
> > behavior of producing distracting and pointless commentary, and
> > inability to adapt to feedback. Please feel free to also ignore emails
> > from them.
> * Do you care for any spell checking?
No.
> * Do you find any related advice (from other automated responses) helpful?
No.
Powered by blists - more mailing lists