mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, hkallweit1@gmail.com,
	linux@armlinux.org.uk, davem@davemloft.net, kuba@kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: phy: broadcom: Enable 10BaseT DAC early wake
Date: Fri, 17 Sep 2021 02:20:08 +0000	[thread overview]
Message-ID: <163184520801.4672.16049058570894189047.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210916212742.1653088-1-f.fainelli@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Thu, 16 Sep 2021 14:27:41 -0700 you wrote:
> Enable the DAC early wake when then link operates at 10BaseT allows
> power savings in the hundreds of milli Watts by shutting down the
> transmitter. A number of errata have been issued for various Gigabit
> PHYs and the recommendation is to enable both the early and forced DAC
> wake to be on the safe side. This needs to be done dynamically based
> upon the link state, which is why a link_change_notify callback is
> utilized.
> 
> [...]

Here is the summary with links:
  - [net-next,v2] net: phy: broadcom: Enable 10BaseT DAC early wake
    https://git.kernel.org/netdev/net-next/c/8dc84dcd7f74

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



      reply	other threads:[~2021-09-17  2:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16 21:27 Florian Fainelli
2021-09-17  2:20 ` 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=163184520801.4672.16049058570894189047.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.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

all inboxes | Powered by JetHome®