From: Herve Codina <herve.codina@bootlin.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Andi Shyti <andi.shyti@kernel.org>
Cc: linux-i2c@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 0/1] lan966x pci device: Add support for SFPs, clock dependency part
Date: Mon, 11 May 2026 18:13:34 +0200 [thread overview]
Message-ID: <20260511181334.26fc869f@bootlin.com> (raw)
In-Reply-To: <20260511160128.34786-1-herve.codina@bootlin.com>
Hi Wolfram, Andi,
On Mon, 11 May 2026 18:01:26 +0200
Herve Codina <herve.codina@bootlin.com> wrote:
> Hi,
>
> Previously, I sent a big picture series adding support for SFP ports
> available on the LAN966x PCI device [0].
>
> In this series patches touch several parts and sub-system in the kernel.
> Reviews have be done and it makes sense to split the series and send
> parts separately.
>
> This current series is the extraction of a patch related to a clock
> build dependency issues.
Oups, this was not the correct series.
Nothing to do with i2c. A wrong command on my side.
The serie has been already sent to correct (clock) maintainers.
Please ignore this one on i2c side.
Sorry for the noise.
Best regards,
Hervé
next prev parent reply other threads:[~2026-05-11 16:13 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-05-11 16:13 ` 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
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=20260511181334.26fc869f@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=allan.nielsen@microchip.com \
--cc=andi.shyti@kernel.org \
--cc=daniel.machon@microchip.com \
--cc=horatiu.vultur@microchip.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=steen.hegelund@microchip.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=wsa+renesas@sang-engineering.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