From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: Shiji Yang <yangshiji66@outlook.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 0/2] pwm: mediatek: fix mt7628 register offset and clock source
Date: Sat, 23 May 2026 18:57:27 +0200 [thread overview]
Message-ID: <ahHcHJNv49ASIshG@monoceros> (raw)
In-Reply-To: <ac6OYRkiDt_OJVcp@monoceros>
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
hello,
On Thu, Apr 02, 2026 at 05:44:32PM +0200, Uwe Kleine-König wrote:
> Hello,
>
> On Tue, Feb 24, 2026 at 04:51:00PM +0800, Shiji Yang wrote:
> > This patch series fixes support for mt7628.
>
> The series looks reasonable to me. It would be great to get some
> feedback from the Mediatek maintainers, though?!
I applied the two patches now without further feedback to
https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git pwm/fixes
. Not sure yet if I send this branch to Linus before 7.1, but it will be
part of 7.2-rc1 for sure.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-05-23 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 8:51 [PATCH 0/2] pwm: mediatek: fix mt7628 register offset and clock source Shiji Yang
2026-02-24 8:51 ` [PATCH 1/2] pwm: mediatek: set mt7628 pwm45_fixup flag to false Shiji Yang
2026-02-24 8:51 ` [PATCH 2/2] pwm: mediatek: correct mt7628 clock source setting Shiji Yang
2026-04-02 15:44 ` [PATCH 0/2] pwm: mediatek: fix mt7628 register offset and clock source Uwe Kleine-König
2026-05-23 16:57 ` Uwe Kleine-König [this message]
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=ahHcHJNv49ASIshG@monoceros \
--to=ukleinek@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=yangshiji66@outlook.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