[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44e48ee7-07a8-4bbc-a98b-095bb1d585a0@linux.microsoft.com>
Date: Mon, 30 Jun 2025 15:23:36 -0700
From: Easwar Hariharan <eahariha@...ux.microsoft.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: eahariha@...ux.microsoft.com,
Louis-Alexis Eyraud <louisalexis.eyraud@...labora.com>,
Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
kernel@...labora.com, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org,
NĂcolas F. R. A. Prado <nfraprado@...labora.com>
Subject: Re: [PATCH] Input: mtk-pmic-keys: Fix null pointer dereference when
no compatible data
On 6/30/2025 2:46 PM, Dmitry Torokhov wrote:
> On Mon, Jun 30, 2025 at 01:18:40PM -0700, Easwar Hariharan wrote:
>>
>> Also, it may make sense to CC: stable@...r.kernel.org for backports
>
> What for? Stable does not need a patch papering over an oops, it needs a
> patch making the keypad working on the affected device.
>
> Thanks.
>
I don't have a stake either way, it was simply a suggestion, since it qualifies
IMHO, per https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html,
the patch "...fixes a problem like an oops..."
The proper fix might well be, as Nicolas suggested, adding the required compatibles.
- Easwar (he/him)
Powered by blists - more mailing lists