[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <094fbb0c-099c-4839-b2c5-162775e35710@moroto.mountain>
Date: Wed, 5 Jun 2024 10:09:14 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Dmitry Yashin <dmt.yashin@...il.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Heiko Stuebner <heiko@...ech.de>,
Luca Ceresoli <luca.ceresoli@...tlin.com>,
Jianqun Xu <jay.xu@...k-chips.com>, Jonas Karlman <jonas@...boo.se>,
devicetree@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/2] pinctrl: rockchip: delay recalced_mask and
route_mask init
On Tue, Jun 04, 2024 at 07:10:19PM +0500, Dmitry Yashin wrote:
> For some SoC's like rk3308 additional runtime setup needed, so delay
> recalced_mask and route_mask init.
>
> Signed-off-by: Dmitry Yashin <dmt.yashin@...il.com>
This sounds like it needs a Fixes tag. Should it be backported to
stable?
I understand that you only know that rk3308 is affected, and probably
you worry that other devices are as well? Just do your best on trying
to figure out which is the first commit where this bug started to
matter. Any information is better than no information.
The commit message should say what the bug looks like to the user. Why
would a user want this patch? I can probably figure it out from reading
the code, but I shouldn't have to.
regards,
dan carpenter
Powered by blists - more mailing lists