[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <akavphbw2wh5vga3eoe6abqdawdssko4cy2sz7oedef4jvzunn@37whg62gmfoh>
Date: Wed, 6 Aug 2025 09:49:52 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: Julien Massot <julien.massot@...labora.com>, kernel@...labora.com,
Matthias Brugger <matthias.bgg@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 1/3] Input: mtk-pmic-keys - MT6359 has a specific release
irq
On Mon, Aug 04, 2025 at 10:05:21AM +0200, AngeloGioacchino Del Regno wrote:
> Il 01/08/25 15:16, Julien Massot ha scritto:
> > A recent commit in linux-next added support for key events.
> > However, the key release event is not properly handled: only key press events
> > are generated, leaving key states stuck in "pressed".
> >
> > This patch ensures that both key press and key release events are properly
> > emitted by handling the release logic correctly.
> >
> > Note: the code was introduced in linux-next by commit
> > bc25e6bf032e ("Input: mtk-pmic-keys - add support for MT6359 PMIC keys")
> > and is not yet present in mainline.
> >
> > Signed-off-by: Julien Massot <julien.massot@...labora.com>
>
> Well, you are effectively fixing the commit that you pointed out, so this needs
>
> Fixes: bc25e6bf032e ("Input: mtk-pmic-keys - add support for MT6359 PMIC keys")
>
> and
>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
I am really interested in how exactly this was developed, tested, and
reviewed...
Thanks.
--
Dmitry
Powered by blists - more mailing lists