From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Cc: andrew@lunn.ch, hkallweit1@gmail.com,
florian.fainelli@broadcom.com, olteanv@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, chester.a.unal@arinc9.com,
daniel@makrotopia.org, dqfext@gmail.com, sean.wang@mediatek.com,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
nicolas.ferre@microchip.com, claudiu.beznea@tuxon.dev,
madalin.bucur@nxp.com, sean.anderson@seco.com,
marcin.s.wojtas@gmail.com, taras.chornyi@plvision.eu,
alexanderduyck@fb.com, kernel-team@meta.com,
horatiu.vultur@microchip.com, UNGLinuxDriver@microchip.com,
Steen.Hegelund@microchip.com, daniel.machon@microchip.com,
radhey.shyam.pandey@amd.com, michal.simek@amd.com,
ioana.ciornei@nxp.com, lynxis@fe80.eu, clement.leger@bootlin.com,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH net-next v2] net: remove phylink_pcs .neg_mode boolean
Date: Sat, 15 Feb 2025 01:20:38 +0000 [thread overview]
Message-ID: <173958243825.2159741.12525730465881025727.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <E1tidPn-0040hd-2R@rmk-PC.armlinux.org.uk>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 13 Feb 2025 17:54:19 +0000 you wrote:
> As all PCS are using the neg_mode parameter rather than the legacy
> an_mode, remove the ability to use the legacy an_mode. We remove the
> tests in the phylink code, unconditionally passing the PCS neg_mode
> parameter to PCS methods, and remove setting the flag from drivers.
>
> Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
>
> [...]
Here is the summary with links:
- [net-next,v2] net: remove phylink_pcs .neg_mode boolean
https://git.kernel.org/netdev/net-next/c/de38503b74e2
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:[~2025-02-15 1:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 17:54 [PATCH net-next v2] net: remove phylink_pcs .neg_mode boolean Russell King (Oracle)
2025-02-15 1: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=173958243825.2159741.12525730465881025727.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexanderduyck@fb.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chester.a.unal@arinc9.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=clement.leger@bootlin.com \
--cc=daniel.machon@microchip.com \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=ioana.ciornei@nxp.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lynxis@fe80.eu \
--cc=madalin.bucur@nxp.com \
--cc=marcin.s.wojtas@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=sean.anderson@seco.com \
--cc=sean.wang@mediatek.com \
--cc=taras.chornyi@plvision.eu \
/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