mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Marek Vasut <marex@nabladev.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	andrew+netdev@lunn.ch, xiaoning.wang@nxp.com,
	claudiu.manoil@nxp.com, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, vladimir.oltean@nxp.com, wei.fang@nxp.com,
	imx@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [net,PATCH] Revert "enetc: Increase eMDIO MDC rate to 2.5 MHz"
Date: Wed, 21 Oct 2026 03:00:04 +0000	[thread overview]
Message-ID: <179255160477.350120.6545435189269879126.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261016185817.54096-1-marex@nabladev.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 16 Oct 2026 20:57:38 +0200 you wrote:
> This reverts commit 587acb86d6465efdc03f6d8524461e6e725597b7.
> 
> While the i.MX95 MDIO MDC clock is improved by the commit
> 587acb86d646 ("enetc: Increase eMDIO MDC rate to 2.5 MHz"),
> other SoCs use different base clock for their MDIO and the
> MDC clock on those SoCs is set out of specification by the
> aforementioned commit. The fix for the i.MX95 MDIO MDC has
> to be done differently, and will be done so in a follow up
> change. Until that is done, revert the commit to fix the
> other SoCs.
> 
> [...]

Here is the summary with links:
  - [net] Revert "enetc: Increase eMDIO MDC rate to 2.5 MHz"
    https://git.kernel.org/netdev/net-next/c/4a929eba247b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-21  3:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 18:57 Marek Vasut
2026-10-16 19:03 ` netdev-bot+sinfo
2026-10-17  2:11 ` Wei Fang
2026-10-21  3:00 ` patchwork-bot+netdevbpf [this message]

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=179255160477.350120.6545435189269879126.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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=marex@nabladev.com \
    --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®