From: Ryan Brue <ryanbrue.dev@gmail.com>
To: Jerome Brunet <jbrunet@baylibre.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.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: Sun, 1 Nov 2026 21:31:27 -0600 [thread overview]
Message-ID: <f98c2746-a025-4a13-9e6f-2ed9fa183fad@gmail.com> (raw)
In-Reply-To: <1jy0brgpez.fsf@starbuckisacylon.baylibre.com>
Hi Jerome,
On 10/21/26 8:21 AM, Jerome Brunet wrote:
> Hi Ryan,
>
> If you do not see it in the clk-next now, it means we missed it and it
> too late for this cycle, sorry.
No worries! I appreciate the response.
Angelo, since you're sending the MediaTek clk pull requests from this
cycle on, could you apply this series and the mt8173-mfgtop fix [1] in
your first one? I checked that both still apply cleanly to -rc1.
[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-11-02 3:31 UTC|newest]
Thread overview: 10+ 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
2026-10-21 13:21 ` Jerome Brunet
2026-11-02 3:31 ` 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=f98c2746-a025-4a13-9e6f-2ed9fa183fad@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