From: Greg KH <gregkh@linuxfoundation.org>
To: "Uwe Kleine-König" <ukleinek@kernel.org>
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org,
nicolas.frattaroli@collabora.com,
Heiko Stuebner <heiko@sntech.de>
Subject: Re: Patch "pwm: rockchip: Round period/duty down on apply, up on get" has been added to the 6.16-stable tree
Date: Tue, 12 Aug 2025 12:53:49 +0200 [thread overview]
Message-ID: <2025081209-vista-preorder-bd6f@gregkh> (raw)
In-Reply-To: <tjogt2ovj4afxo3lz7ydwsqtk4b52gjvga47es6x3ogdbfopyb@weiw3effavjh>
On Tue, Aug 12, 2025 at 12:36:48PM +0200, Uwe Kleine-König wrote:
> Hello Greg,
>
> On Tue, Aug 12, 2025 at 10:53:11AM +0200, Greg KH wrote:
> > On Sat, Aug 09, 2025 at 11:45:23AM +0200, Uwe Kleine-König wrote:
> > > while the new code makes the driver match the PWM rules now, I'd be
> > > conservative and not backport that patch because while I consider it a
> > > (very minor) fix that's a change in behaviour and maybe people depend on
> > > that old behaviour. So let's not break our user's workflows and reserve
> > > that for a major release. Please drop this patch from your queue.
> >
> > Now dropped, but note, any behavior change is ok for ANY kernel version
> > as we guarantee they all work the same :)
>
> Your statement makes no sense, I guess you missed to add a "don't".
> Otherwise I'd like to know who "we" is :-)
{sigh} yes, I mean "any behavior change is NOT ok..."
sorry,
greg k-h
next prev parent reply other threads:[~2025-08-12 10:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250808223033.1417018-1-sashal@kernel.org>
2025-08-09 9:45 ` Patch "pwm: rockchip: Round period/duty down on apply, up on get" has been added to the 6.16-stable tree Uwe Kleine-König
2025-08-12 8:53 ` Greg KH
2025-08-12 10:36 ` Uwe Kleine-König
2025-08-12 10:53 ` Greg KH [this message]
2025-08-12 20:15 ` Uwe Kleine-König
2025-08-13 13:30 ` Nicolas Frattaroli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025081209-vista-preorder-bd6f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=nicolas.frattaroli@collabora.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=ukleinek@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox