[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <71bb9475-07ba-48a9-9fa4-76e18a310b3a@gmail.com>
Date: Tue, 21 Oct 2025 09:55:22 +0100
From: Mehdi Ben Hadj Khelifa <mehdi.benhadjkhelifa@...il.com>
To: Javier Martinez Canillas <javierm@...hat.com>,
Shuah Khan <skhan@...uxfoundation.org>, maarten.lankhorst@...ux.intel.com,
mripard@...nel.org, tzimmermann@...e.de, airlied@...il.com, simona@...ll.ch
Cc: dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
david.hunter.linux@...il.com, khalid@...nel.org,
linux-kernel-mentees@...ts.linuxfoundation.org
Subject: Re: [PATCH] drm/solomon: Use kmalloc_array() instead of kmalloc()
On 10/21/25 8:51 AM, Javier Martinez Canillas wrote:
> Mehdi Ben Hadj Khelifa <mehdi.benhadjkhelifa@...il.com> writes:
>
> Hello Mehdi,
>
>> On 10/20/25 9:56 PM, Shuah Khan wrote:
>
> [...]
>
>>>> I have a raspberrypi zero 2 wh that i'm using in combination with the
>>>> ssd1306 OLED panel via I2C to test it's rendering and it's working
>>>> properly by using modetest and seeing no regressions or warnings in
>>>> dmesg.
>>>>
>>>
>>> Send v2 with all these details and why this change is needed
>>> in the first place.
>>>
>> Okay, I will do that as soon as possible.> When and how does this
>> potential problem trigger? Is this a
>>> theoretical or does this happen in this code path and how?
>>> Next time include all of these details people understand the
>>> problem better.
>>>
>> We'll do in the next iteration.Thanks
>>
>
> A similar patch was posted by another developer a couple of weeks
> ago and is now queued already in the drm-misc-next branch:
>
> https://cgit.freedesktop.org/drm/drm-misc/commit/?id=940dd88c5f5bdb1f3e19873a856a677ebada63a9
>
Hello javier,
Thanks for the heads up. I will abort working on the patch.
Best Regards,
Mehdi Ben Hadj Khelifa
Powered by blists - more mailing lists