All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Lukasz Majewski <lukma@denx.de>
Cc: Tristram.Ha@microchip.com, edumazet@google.com, andrew@lunn.ch,
	davem@davemloft.net, woojung.huh@microchip.com,
	olteanv@gmail.com, o.rempel@pengutronix.de, f.fainelli@gmail.com,
	kuba@kernel.org, pabeni@redhat.com, UNGLinuxDriver@microchip.com,
	linux@armlinux.org.uk, hkallweit1@gmail.com, michael@walle.cc,
	horatiu.vultur@microchip.com, arun.ramadoss@microchip.com,
	linux@rempel-privat.de, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [net v4] net: phy: Provide Module 4 KSZ9477 errata (DS80000754C)
Date: Thu, 07 Sep 2023 04:00:22 +0000	[thread overview]
Message-ID: <169405922245.5293.2774617542441865085.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230905093315.784052-1-lukma@denx.de>

Hello:

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

On Tue,  5 Sep 2023 11:33:15 +0200 you wrote:
> The KSZ9477 errata points out (in 'Module 4') the link up/down problems
> when EEE (Energy Efficient Ethernet) is enabled in the device to which
> the KSZ9477 tries to auto negotiate.
> 
> The suggested workaround is to clear advertisement of EEE for PHYs in
> this chip driver.
> 
> [...]

Here is the summary with links:
  - [net,v4] net: phy: Provide Module 4 KSZ9477 errata (DS80000754C)
    https://git.kernel.org/netdev/net/c/08c6d8bae48c

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



      parent reply	other threads:[~2023-09-07  4:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05  9:33 [net v4] net: phy: Provide Module 4 KSZ9477 errata (DS80000754C) Lukasz Majewski
2023-09-05 20:48 ` Jakub Kicinski
2023-09-06  7:33   ` Lukasz Majewski
2023-09-05 21:58 ` Florian Fainelli
2023-09-05 22:29 ` Vladimir Oltean
2023-09-06  6:40   ` Russell King (Oracle)
2023-09-07  4: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=169405922245.5293.2774617542441865085.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Tristram.Ha@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=arun.ramadoss@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=horatiu.vultur@microchip.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linux@rempel-privat.de \
    --cc=lukma@denx.de \
    --cc=michael@walle.cc \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=woojung.huh@microchip.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.