From: Herve Codina <herve.codina@bootlin.com>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: 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 v7 1/1] clk: lan966x: Add MCHP_LAN966X_PCI dependency
Date: Fri, 5 Jun 2026 08:22:36 +0200 [thread overview]
Message-ID: <20260605082236.6fc9f76d@bootlin.com> (raw)
In-Reply-To: <20260511160113.34755-2-herve.codina@bootlin.com>
Hi,
On Mon, 11 May 2026 18:01:12 +0200
Herve Codina <herve.codina@bootlin.com> 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>
> ---
> drivers/clk/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
IMHO, the patch is ready to be applied.
What is your opinion?
Best regards,
Hervé
next prev parent reply other threads:[~2026-06-05 6:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 16:01 [PATCH v7 0/1] lan966x pci device: Add support for SFPs, clock dependency part Herve Codina
2026-05-11 16:01 ` [PATCH v7 1/1] clk: lan966x: Add MCHP_LAN966X_PCI dependency Herve Codina
2026-06-05 6:22 ` Herve Codina [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-11 16:01 [PATCH v7 0/1] lan966x pci device: Add support for SFPs, clock dependency part Herve Codina
2026-05-11 16:01 ` [PATCH v7 1/1] clk: lan966x: Add MCHP_LAN966X_PCI dependency Herve Codina
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=20260605082236.6fc9f76d@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=allan.nielsen@microchip.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 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.