[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3ab331db-363c-46c3-8e9f-0cbf4d142493@web.de>
Date: Fri, 27 Dec 2024 11:24:13 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Karan Sanghavi <karansanghvi98@...il.com>,
dri-devel@...ts.freedesktop.org, linux-mediatek@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org
Cc: Alexandre Mergnat <amergnat@...libre.com>,
Angelo Gioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
Chun-Kuang Hu <chunkuang.hu@...nel.org>, David Airlie <airlied@...il.com>,
Matthias Brugger <matthias.bgg@...il.com>,
Philipp Zabel <p.zabel@...gutronix.de>,
Shuah Khan <skhan@...uxfoundation.org>, Simona Vetter <simona@...ll.ch>,
Sui Jingfeng <sui.jingfeng@...ux.dev>, LKML <linux-kernel@...r.kernel.org>,
CK Hu (胡俊光) <ck.hu@...iatek.com>
Subject: Re: drm/mediatek: Initialize pointer before use to avoid undefiend
behaviour
>> …
>>> ---
>>> Coverity Message:
>>> CID 1601557: (#1 of 1): Uninitialized pointer read (UNINIT)
>>> 3. uninit_use: Using uninitialized value next.
>>
>> May such information become a part for the final change description?
>>
> Ofcourse, it shouldn't be the part of the change description.
I suggest to reconsider this view once more.
> it is just for the reference to understand more about what the error message
> is generated by coverity scan.
Please take another look at possibilities how other contributors indicated
that some change opportunities were pointed out by advanced source code
analysis tools.
Regards,
Markus
Powered by blists - more mailing lists