From: Herve Codina <herve.codina@bootlin.com>
To: Brian Masney <bmasney@redhat.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Allan Nielsen <allan.nielsen@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Daniel Machon <daniel.machon@microchip.com>,
Steen Hegelund <steen.hegelund@microchip.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v8 1/1] clk: lan966x: Add MCHP_LAN966X_PCI dependency
Date: Fri, 17 Jul 2026 12:13:44 +0200 [thread overview]
Message-ID: <20260717121344.38a6a0f9@bootlin.com> (raw)
In-Reply-To: <akvcmiJtO4LpHA2N@redhat.com>
Hi Maintainers,
On Mon, 6 Jul 2026 12:49:30 -0400
Brian Masney <bmasney@redhat.com> wrote:
> On Tue, Jun 30, 2026 at 12:30:50PM +0200, Herve Codina wrote:
> > The lan966x clock controller depends on the LAN969x architecture or the
> > LAN966x SoC.
> >
> > This clock controller can be used by the LAN966x PCI device and so it
> > needs to be available when the LAN966x PCI device is enabled.
> >
> > Signed-off-by: Herve Codina <herve.codina@bootlin.com>
> > Acked-by: Stephen Boyd <sboyd@kernel.org>
>
> Reviewed-by: Brian Masney <bmasney@redhat.com>
>
IMHO, this patch is ready to be applied.
Let me know if I need to do anything else on my side to move forward.
Best regards,
Hervé
next prev parent reply other threads:[~2026-07-17 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 10:30 [PATCH v8 0/1] lan966x pci device: Add support for SFPs, clock dependency part Herve Codina
2026-06-30 10:30 ` [PATCH v8 1/1] clk: lan966x: Add MCHP_LAN966X_PCI dependency Herve Codina
2026-07-06 16:49 ` Brian Masney
2026-07-17 10:13 ` Herve Codina [this message]
2026-07-17 15:03 ` Brian Masney
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=20260717121344.38a6a0f9@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=allan.nielsen@microchip.com \
--cc=bmasney@redhat.com \
--cc=daniel.machon@microchip.com \
--cc=horatiu.vultur@microchip.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=steen.hegelund@microchip.com \
--cc=thomas.petazzoni@bootlin.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