From: "Łukasz Majewski" <lukma@nabladev.com>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>
Cc: Peng Fan <peng.fan@oss.nxp.com>, Abel Vesa <abelvesa@kernel.org>,
Peng Fan <peng.fan@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/4] clk: vf610: Add clocks to support MTIP L2 switch
Date: Mon, 16 Feb 2026 12:33:12 +0100 [thread overview]
Message-ID: <20260216123312.4a310b39@wsk> (raw)
In-Reply-To: <jk6roonftm44qwnyxezhukdoqahrj2l7zaa55w35oq3uj4en4w@obfufdazx3wb>
Hi Abel,
> On 26-02-16 10:15:38, Łukasz Majewski wrote:
> > Dear all,
> >
> > > On Thu, Jan 29, 2026 at 10:54:38AM +0100, Lukasz Majewski wrote:
> > > >This patch series:
> > > >- cleans up clocks' setup on vf610 by moving VF610_CLK_END define
> > > > to driver code
> > > >- introduces support for several clocks required by MTIP switch
> > > >IP block
> > > >
> > > >Lukasz Majewski (4):
> > > > clk: vf610: Move VF610_CLK_END define to clk-vf610 driver
> > > > dt-bindings: clock: vf610: Drop VF610_CLK_END define
> > > > dt-bindings: clock: vf610: Add definitions for MTIP L2 switch
> > > > clk: vf610: Add support for the Ethernet switch clocks
> > >
> > > Reviewed-by: Peng Fan <peng.fan@nxp.com>
> >
> > Gentle ping regarding this patch set...
>
> Will apply after rc1.
Thanks :-)
--
Best regards,
Lukasz Majewski
--
Nabla Software Engineering GmbH
HRB 40522 Augsburg
Phone: +49 821 45592596
E-Mail: office@nabladev.com
Managing Director : Stefano Babic
next prev parent reply other threads:[~2026-02-16 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 9:54 [PATCH v4 0/4] clk: vf610: Add clocks to support MTIP L2 switch Lukasz Majewski
2026-01-29 9:54 ` [PATCH v4 1/4] clk: vf610: Move VF610_CLK_END define to clk-vf610 driver Lukasz Majewski
2026-01-29 9:54 ` [PATCH v4 2/4] dt-bindings: clock: vf610: Drop VF610_CLK_END define Lukasz Majewski
2026-01-29 16:56 ` Rob Herring (Arm)
2026-01-29 9:54 ` [PATCH v4 3/4] dt-bindings: clock: vf610: Add definitions for MTIP L2 switch Lukasz Majewski
2026-01-29 16:57 ` Rob Herring (Arm)
2026-01-29 9:54 ` [PATCH v4 4/4] clk: vf610: Add support for the Ethernet switch clocks Lukasz Majewski
2026-02-02 1:56 ` [PATCH v4 0/4] clk: vf610: Add clocks to support MTIP L2 switch Peng Fan
2026-02-16 9:15 ` Łukasz Majewski
2026-02-16 10:32 ` Abel Vesa
2026-02-16 11:33 ` Łukasz Majewski [this message]
2026-03-18 15:39 ` Abel Vesa
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=20260216123312.4a310b39@wsk \
--to=lukma@nabladev.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.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