[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8e4fe108-cfde-40c0-83f5-c1ce60b0940f@web.de>
Date: Sun, 6 Oct 2024 13:12:26 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Zichen Xie <zichenxie0106@...il.com>, alsa-devel@...a-project.org,
linux-sound@...r.kernel.org, linux-arm-msm@...r.kernel.org
Cc: 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: ASoC: qcom: Fix NULL Dereference in
asoc_qcom_lpass_cpu_platform_probe()
>>>>> 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.
…
>> * Do you care for any spell checking?
>
> No.
I find such a feedback surprising.
Does it indicate any recurring communication difficulties?
>> * Do you find any related advice (from other automated responses) helpful?
>
> No.
I wonder how this answer fits to reminders for the Linux patch review process
(which were also automatically sent) according to your inbox filter rules.
Regards,
Markus
Powered by blists - more mailing lists