Re: [PATCH 6.18 000/614] 6.18.2-rc1 review

[Ronald Warsow <rwarsow@gmx.de>]

On 17.12.25 10:36, Greg Kroah-Hartman wrote:
> On Wed, Dec 17, 2025 at 09:27:49AM +0100, Ronald Warsow wrote:
>> On 17.12.25 06:47, Greg Kroah-Hartman wrote:
>>> On Tue, Dec 16, 2025 at 05:06:56PM +0100, Ronald Warsow wrote:
>>>> Hi
...

>>>> If I did the bisect correct, bisect-log:
>>>>
>>>> # status: waiting for both good and bad commits
>>>> # good: [25442251cbda7590d87d8203a8dc1ddf2c93de61] Linux 6.18.1
>>>> git bisect good 25442251cbda7590d87d8203a8dc1ddf2c93de61
>>>> # status: waiting for bad commit, 1 good commit known
>>>> # bad: [103c79e44ce7c81882928abab98b96517a8bce88] Linux 6.18.2-rc1
>>>> git bisect bad 103c79e44ce7c81882928abab98b96517a8bce88
>>>> # bad: [d32e7ccac8c6afc6a3a46fa4e7cdf0568ee919bd] drm/msm: Fix NULL pointer
>>>> dereference in crashstate_get_vm_logs()
>>>> git bisect bad d32e7ccac8c6afc6a3a46fa4e7cdf0568ee919bd
>>>
>>> Is this also an issue with 6.19-rc1?  Are we missing something here?
>>>
>> 6.19-rc1 is okay here
> 
> Odd, as you aren't even running the driver that this commit points to,
> right?  You shouldn't be building it, so why does this show up as the
> "bad" commit id?
> 

maybe I did something wrong with bisect ?
- I'm no developer and not very experienced with it -


side note: tomorrow I'm in vacation

> totally confused,
> 
> greg k-h