From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Sven Van Asbroeck <TheSven73@gmail.com>,
Clemens Gruber <clemens.gruber@pqgruber.com>,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
linux-pwm@vger.kernel.org
Subject: PWM-Patches for next merge window [Was: Re: [PATCH 1/4] pwm: core: Support new usage_power setting in PWM] state
Date: Mon, 21 Jun 2021 08:47:45 +0200 [thread overview]
Message-ID: <20210621064745.v7ndjlybjav7ai6y@pengutronix.de> (raw)
In-Reply-To: <YMIPjGtYfby6ZXKl@orome.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 1573 bytes --]
Hello Thierry,
On Thu, Jun 10, 2021 at 03:11:40PM +0200, Thierry Reding wrote:
> On Wed, Jun 09, 2021 at 10:41:44PM +0200, Uwe Kleine-König wrote:
> > On Mon, Jun 07, 2021 at 08:51:58PM +0200, Uwe Kleine-König wrote:
> > > My problem is not that in the end a solution is picked that wasn't my
> > > favourite. My problem is that I have the impression my arguments were
> > > not considered but simply ignored.
> >
> > Another thing that annoys me is that there are currently ~20 open
> > patches by me in patchwork, most of them are easy to understand cleanups
> > and fixes, most of them are older than Clemens' series and most of them
> > are uncommented by you. And in this situation you apply the only
> > controversial series.
>
> Clemens' series is actually older than those cleanups because it's been
> in the works for many months now. And the reason why I'm prioritizing
> Clemens' series is because it has broader impact and I want to make sure
> it gets maximum soaking time in linux-next.
Hmm, I would have done that differently, but I don't expect that you
expected agreement from my side.
> Small fixes and cleanups are less likely to break things, so I'm going
> to apply them after.
I wonder what's the ideal delay for fixes and cleanups in your book.
We're two weeks after merging that high-impact patch series and Linus
just released -rc7.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-06-21 6:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 13:18 [PATCH 1/4] pwm: core: Support new usage_power setting in PWM state Clemens Gruber
2021-05-07 13:18 ` [PATCH 2/4] pwm: pca9685: " Clemens Gruber
2021-05-07 13:18 ` [PATCH 3/4] pwm: pca9685: Restrict period change for enabled PWMs Clemens Gruber
2021-05-07 13:18 ` [PATCH 4/4] pwm: pca9685: Add error messages for failed regmap calls Clemens Gruber
2021-05-07 15:03 ` [PATCH 1/4] pwm: core: Support new usage_power setting in PWM state Uwe Kleine-König
2021-05-07 15:47 ` Clemens Gruber
2021-05-07 23:18 ` Uwe Kleine-König
2021-05-31 16:12 ` Clemens Gruber
2021-06-04 9:49 ` Thierry Reding
2021-06-07 6:08 ` Uwe Kleine-König
2021-06-07 14:40 ` Thierry Reding
2021-06-07 18:51 ` Uwe Kleine-König
2021-06-09 20:41 ` Uwe Kleine-König
2021-06-10 13:11 ` Thierry Reding
2021-06-21 6:47 ` Uwe Kleine-König [this message]
2021-06-25 9:55 ` PWM-Patches for next merge window Uwe Kleine-König
2021-06-04 9:44 ` [PATCH 1/4] pwm: core: Support new usage_power setting in PWM state Thierry Reding
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=20210621064745.v7ndjlybjav7ai6y@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=TheSven73@gmail.com \
--cc=clemens.gruber@pqgruber.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).