From: Brian Masney <bmasney@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>,
"Tero Kristo" <kristo@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Tony Lindgren" <tony@atomide.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Théo Lebrun" <theo.lebrun@bootlin.com>,
"Grégory Clement" <gregory.clement@bootlin.com>,
linux-omap@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Matti Vaittinen" <mazziesaccount@gmail.com>
Subject: Re: [PATCH v2 1/2] clk: ti: mux: resolve parent clocks by DT index, not by name
Date: Wed, 19 Aug 2026 17:25:14 -0400 [thread overview]
Message-ID: <aoYfOvi6B6ZGCMY4@redhat.com> (raw)
In-Reply-To: <CAMuHMdUsupXQb7Y59ri8wtrjixPpWoLRk5SsuieZLjKG4Y+gwA@mail.gmail.com>
On Wed, Aug 19, 2026 at 09:13:08PM +0200, Geert Uytterhoeven wrote:
> I submitted a first set of fixes, incl. "[PATCH treewide 1/5] clk:
> ti: Make sure clk_init_data is fully initialized"
> https://lore.kernel.org/e6f52b34163c8e708c1100107b437af0b3b049a6.1787165329.git.geert+renesas@glider.be/
> I will submit the remainder (way too many) later...
Thanks Geert for posting that!
Stephen: You can ignore my message about backing out Mathieu's two
patches. We should just pick up what Geert posted.
Brian
next prev parent reply other threads:[~2026-08-19 21:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 7:41 [PATCH v2 0/2] clk: ti: mux: resolve parent clocks by DT index, not by name Mathieu Dubois-Briand
2026-07-27 7:41 ` [PATCH v2 1/2] " Mathieu Dubois-Briand
2026-07-28 14:11 ` Brian Masney
2026-08-14 5:43 ` Stephen Boyd
2026-08-18 16:02 ` Geert Uytterhoeven
2026-08-18 21:13 ` Brian Masney
2026-08-19 5:39 ` Mathieu Dubois-Briand
2026-08-19 12:32 ` Geert Uytterhoeven
2026-08-19 15:12 ` Mathieu Dubois-Briand
2026-08-19 19:13 ` Geert Uytterhoeven
2026-08-19 21:25 ` Brian Masney [this message]
2026-07-27 7:41 ` [PATCH v2 2/2] clk: ti: composite: " Mathieu Dubois-Briand
2026-07-28 14:11 ` Brian Masney
2026-08-14 5:43 ` Stephen Boyd
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=aoYfOvi6B6ZGCMY4@redhat.com \
--to=bmasney@redhat.com \
--cc=geert@linux-m68k.org \
--cc=gregory.clement@bootlin.com \
--cc=kristo@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=mazziesaccount@gmail.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=theo.lebrun@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.