From: Marek Vasut <marex@nabladev.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Wei Fang <wei.fang@nxp.com>, Clark Wang <xiaoning.wang@nxp.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
"David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [net-next,PATCH v2] enetc: Increase eMDIO MDC rate to 2.5 MHz
Date: Fri, 2 Oct 2026 01:11:36 +0200 [thread overview]
Message-ID: <6b22d5e7-1f94-4c3c-8a0e-5c5573c4c7cb@nabladev.com> (raw)
In-Reply-To: <20261001155129.51ea9930@kernel.org>
On 10/2/26 12:51 AM, Jakub Kicinski wrote:
> On Thu, 1 Oct 2026 03:34:09 +0200 Marek Vasut wrote:
>> Jakub, do you want a revert of this one, fix, or follow up patch ?
>
> FWIW the answer was follow up, thanks for sending it!
Of course, sorry for the mess this created.
I'll try to figure out some more flexible way of configuring the MDC
clock together with Wei, basically what Andrew suggested, in another
follow up patch. Hopefully there is a way to do that for all the SoCs
which have this IP.
next prev parent reply other threads:[~2026-10-01 23:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 18:05 Marek Vasut
2026-09-25 18:43 ` netdev-bot+sashiko
2026-09-30 2:10 ` patchwork-bot+netdevbpf
2026-09-30 2:21 ` Marek Vasut
2026-09-30 20:51 ` Jakub Kicinski
2026-09-30 3:40 ` Wei Fang
2026-09-30 4:19 ` Marek Vasut
2026-09-30 6:12 ` Wei Fang
2026-09-30 13:11 ` Andrew Lunn
2026-10-01 0:04 ` Wei Fang
2026-09-30 13:27 ` Marek Vasut
2026-10-01 0:45 ` Wei Fang
2026-10-01 1:34 ` Marek Vasut
2026-10-01 10:57 ` Wei Fang
2026-10-01 13:53 ` Andrew Lunn
2026-10-01 22:43 ` Marek Vasut
2026-10-01 22:51 ` Jakub Kicinski
2026-10-01 23:11 ` Marek Vasut [this message]
2026-10-01 22:00 ` Marek Vasut
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=6b22d5e7-1f94-4c3c-8a0e-5c5573c4c7cb@nabladev.com \
--to=marex@nabladev.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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
all inboxes | Powered by JetHome®