From: Lee Jones <lee@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
William Breathitt Gray <wbg@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-pwm@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Thorsten Scherer <T.Scherer@eckelmann.de>
Subject: Re: [PATCH v2 0/5] mfd: stm32-timers: Make register definition more flexible
Date: Wed, 26 Jun 2024 16:13:43 +0100 [thread overview]
Message-ID: <20240626151343.GA2504017@google.com> (raw)
In-Reply-To: <cover.1718791090.git.u.kleine-koenig@baylibre.com>
On Wed, 19 Jun 2024, Uwe Kleine-König wrote:
> Hello,
>
> (implicit) v1 is available at
> https://lore.kernel.org/lkml/cover.1718352022.git.u.kleine-koenig@baylibre.com
> .
>
> Changes introduced here:
>
> - Split the patch removing TIM_DIER_CC_IE() and use appropriate subject
> prefixes. Lee and William didn't like the patch touching both
> include/linux/mfd/stm32-timers.h and
> drivers/counter/stm32-timer-cnt.c not having a hint to the counter
> subsystem (at least that's my interpretation of their feedback).
> Not mentioning mfd didn't seem to be considerably better in my eyes,
> so I split this patch.
> - Fix typo noticed by Thorsten.
> - Update subject prefix of the last patch to match what is usually done
> for pwm.
>
> I have some further updates to the pwm-stm32 driver that will probably
> go in before v6.10-rc1. They shouldn't conflict, still I'd prefer to let
> the pwm patch go in via my tree as I might have some further changes for
> that driver. So if this is merged using the mfd or counter tree, please
> skip the pwm patch. A stable branch would be welcome in this case.
>
> Best regards
> Uwe
>
>
> Uwe Kleine-König (5):
> mfd: stm32-timers: Unify alignment of register definition
> mfd: stm32-timers: Add some register definitions with a parameter
> counter: stm32-timer-cnt: Use TIM_DIER_CCxIE(x) instead of
> TIM_DIER_CCxIE(x)
> mfd: stm32-timers: Drop unused TIM_DIER_CC_IE
> pwm: stm32: Make use of parametrised register definitions
>
> drivers/counter/stm32-timer-cnt.c | 4 +-
> drivers/pwm/pwm-stm32.c | 22 ++--
> include/linux/mfd/stm32-timers.h | 179 ++++++++++++++++--------------
> 3 files changed, 107 insertions(+), 98 deletions(-)
>
> base-commit: 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0
Applied patches 1-4 and submitted for build testing.
If all is good, I'll sent out a PR for William.
Note to self: ib-mfd-counter-5.11
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-06-26 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 10:11 [PATCH v2 0/5] mfd: stm32-timers: Make register definition more flexible Uwe Kleine-König
2024-06-19 10:11 ` [PATCH v2 1/5] mfd: stm32-timers: Unify alignment of register definition Uwe Kleine-König
2024-06-19 10:11 ` [PATCH v2 2/5] mfd: stm32-timers: Add some register definitions with a parameter Uwe Kleine-König
2024-06-19 10:11 ` [PATCH v2 3/5] counter: stm32-timer-cnt: Use TIM_DIER_CCxIE(x) instead of TIM_DIER_CCxIE(x) Uwe Kleine-König
2024-06-20 8:44 ` Lee Jones
2024-06-20 8:59 ` William Breathitt Gray
2024-06-20 9:32 ` Lee Jones
2024-06-20 10:34 ` Uwe Kleine-König
2024-06-20 17:38 ` Lee Jones
2024-06-20 20:56 ` Uwe Kleine-König
2024-06-26 19:43 ` Uwe Kleine-König
2024-06-26 19:55 ` Uwe Kleine-König
2024-06-19 10:11 ` [PATCH v2 4/5] mfd: stm32-timers: Drop unused TIM_DIER_CC_IE Uwe Kleine-König
2024-06-19 10:11 ` [PATCH v2 5/5] pwm-stm32: Make use of parametrised register definitions Uwe Kleine-König
2024-06-26 15:13 ` Lee Jones [this message]
2024-06-28 14:28 ` [GIT PULL] Immutable branch between MFD and Counter due for the v5.11 merge window Lee Jones
2024-06-28 15:31 ` Uwe Kleine-König
2024-07-03 1:44 ` William Breathitt Gray
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=20240626151343.GA2504017@google.com \
--to=lee@kernel.org \
--cc=T.Scherer@eckelmann.de \
--cc=alexandre.torgue@foss.st.com \
--cc=fabrice.gasnier@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=wbg@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;
as well as URLs for NNTP newsgroup(s).