[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YfALlLgo3MAcbFrZ@swift.blarg.de>
Date: Tue, 25 Jan 2022 15:39:16 +0100
From: Max Kellermann <max@...rg.de>
To: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
Cc: linux-pwm@...r.kernel.org, thierry.reding@...il.com,
lee.jones@...aro.org, linux-kernel@...r.kernel.org,
andrey@...edev.lt, stable@...r.kernel.org
Subject: Re: [PATCH 1/3] pwm-sun4i: convert "next_period" to local variable
On 2022/01/25 15:31, Uwe Kleine-König <u.kleine-koenig@...gutronix.de> wrote:
> I think I'd drop this. This isn't a fix worth on it's own to be
> backported and if this is needed for one of the next patches, the stable
> maintainers will notice themselves (and it might be worth to shuffle
> this series to make the fixes come first).
The first two patches are preparation for the third patch, which fixes
the actual bug.
Of course, I could have done everything in one patch, but I thought
splitting the first two out makes review easier. This way, every step
is almost trivial.
If you want me to fold the three patches into one, I can do that. But
I can't reorder them (or backport only the bug fix to stable).
Max
Powered by blists - more mailing lists