From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <olteanv@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
f.fainelli@gmail.com, andrew@lunn.ch, vivien.didelot@gmail.com,
michael@walle.cc, hkallweit1@gmail.com, linux@armlinux.org.uk,
claudiu.manoil@nxp.com, alexandre.belloni@bootlin.com,
UNGLinuxDriver@microchip.com, vladimir.oltean@nxp.com
Subject: Re: [PATCH net-next] net: dsa: felix: set TX flow control according to the phylink_mac_link_up resolution
Date: Tue, 08 Jun 2021 23:40:05 +0000 [thread overview]
Message-ID: <162319560596.24693.11715284868769075021.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210608111651.4084572-1-olteanv@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Tue, 8 Jun 2021 14:16:51 +0300 you wrote:
> From: Vladimir Oltean <vladimir.oltean@nxp.com>
>
> Instead of relying on the static initialization done by ocelot_init_port()
> which enables flow control unconditionally, set SYS_PAUSE_CFG_PAUSE_ENA
> according to the parameters negotiated by the PHY.
>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
>
> [...]
Here is the summary with links:
- [net-next] net: dsa: felix: set TX flow control according to the phylink_mac_link_up resolution
https://git.kernel.org/netdev/net-next/c/de274be32cb2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-06-08 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 11:16 [PATCH net-next] net: dsa: felix: set TX flow control according to the phylink_mac_link_up resolution Vladimir Oltean
2021-06-08 23:40 ` 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=162319560596.24693.11715284868769075021.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@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;
as well as URLs for NNTP newsgroup(s).