From: Ryan Brue <ryanbrue.dev@gmail.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Chen-Yu Tsai <wenst@chromium.org>
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 2/2] clk: mediatek: mt6795: fix the FHCTL DDS mask width
Date: Sat, 17 Oct 2026 18:03:15 -0500 [thread overview]
Message-ID: <e8389c1c-e858-4171-adff-5bd94909120c@gmail.com> (raw)
In-Reply-To: <12e0953c-5181-45f2-b409-05163ab2a031@collabora.com>
On 9/28/26 7:22 AM, AngeloGioacchino Del Regno wrote:
>
> Please collect the changes that I've reviewed for this cycle... I'll
> start
> sending PRs from the next one.
>
> Thanks!
>
> Cheers,
> Angelo
Hi Brian, Jerome, and Stephen,
Gentle ping, in case these slipped through the collection Angelo asked
for above: this two-patch series (FHCTL DDS mask width, mt8173 and
mt6795) and the related mt8173-mfgtop fix [1], both reviewed by Angelo
on 14 Sep. Neither is in clk-next yet, and both still apply cleanly to
it. If it's too late for this cycle, just let me know, and I'll ask
Angelo to take them in his PR for the next one.
[1]
https://lore.kernel.org/all/20260913-mfgtop-no-clk-api-power-on-v2-1-b84771a3d5bd@gmail.com/
Best regards,
Ryan Brue
prev parent reply other threads:[~2026-10-17 23:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 6:40 [PATCH 0/2] clk: mediatek: Fix FHCTL DDS mask widths for mt8173, mt6795 Ryan Brue
2026-09-12 6:40 ` [PATCH 1/2] clk: mediatek: mt8173: fix the FHCTL DDS mask width Ryan Brue
2026-09-14 8:16 ` AngeloGioacchino Del Regno
2026-09-12 6:40 ` [PATCH 2/2] clk: mediatek: mt6795: " Ryan Brue
2026-09-14 8:16 ` AngeloGioacchino Del Regno
2026-09-25 13:13 ` Jerome Brunet
2026-09-28 12:22 ` AngeloGioacchino Del Regno
2026-10-17 23:03 ` Ryan Brue [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=e8389c1c-e858-4171-adff-5bd94909120c@gmail.com \
--to=ryanbrue.dev@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bmasney+clk@redhat.com \
--cc=jbrunet+clk@baylibre.com \
--cc=jbrunet@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=sboyd@kernel.org \
--cc=wenst@chromium.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
all inboxes | Powered by JetHome®