From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Cc: alexandre.torgue@foss.st.com, joabreu@synopsys.com,
andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
chenfeiyang@loongson.cn, hkallweit1@gmail.com, kuba@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
pabeni@redhat.com, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
vz@mleia.com, kernel@esmil.dk, samin.guo@starfivetech.com,
wens@csie.org, jernej.skrabec@gmail.com, samuel@sholland.org,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
linux-sunxi@lists.linux.dev, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH net-next] net: stmmac: clarify difference between "interface" and "phy_interface"
Date: Mon, 28 Aug 2023 20:00:23 +0000 [thread overview]
Message-ID: <169325282356.23387.6771304913662801847.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <E1qZq83-005tts-6K@rmk-PC.armlinux.org.uk>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 26 Aug 2023 11:02:51 +0100 you wrote:
> Clarify the difference between "interface" and "phy_interface" in
> struct plat_stmmacenet_data, both by adding a comment, and also
> renaming "interface" to be "mac_interface". The difference between
> these are:
>
> MAC ----- optional PCS ----- SerDes ----- optional PHY ----- Media
> ^ ^
> mac_interface phy_interface
>
> [...]
Here is the summary with links:
- [net-next] net: stmmac: clarify difference between "interface" and "phy_interface"
https://git.kernel.org/netdev/net-next/c/a014c35556b9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
Cc: alexandre.torgue@foss.st.com, joabreu@synopsys.com,
andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
chenfeiyang@loongson.cn, hkallweit1@gmail.com, kuba@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
pabeni@redhat.com, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
vz@mleia.com, kernel@esmil.dk, samin.guo@starfivetech.com,
wens@csie.org, jernej.skrabec@gmail.com, samuel@sholland.org,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
linux-sunxi@lists.linux.dev, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH net-next] net: stmmac: clarify difference between "interface" and "phy_interface"
Date: Mon, 28 Aug 2023 20:00:23 +0000 [thread overview]
Message-ID: <169325282356.23387.6771304913662801847.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <E1qZq83-005tts-6K@rmk-PC.armlinux.org.uk>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 26 Aug 2023 11:02:51 +0100 you wrote:
> Clarify the difference between "interface" and "phy_interface" in
> struct plat_stmmacenet_data, both by adding a comment, and also
> renaming "interface" to be "mac_interface". The difference between
> these are:
>
> MAC ----- optional PCS ----- SerDes ----- optional PHY ----- Media
> ^ ^
> mac_interface phy_interface
>
> [...]
Here is the summary with links:
- [net-next] net: stmmac: clarify difference between "interface" and "phy_interface"
https://git.kernel.org/netdev/net-next/c/a014c35556b9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-28 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 10:02 [PATCH net-next] net: stmmac: clarify difference between "interface" and "phy_interface" Russell King (Oracle)
2023-08-26 10:02 ` Russell King (Oracle)
2023-08-28 20:00 ` patchwork-bot+netdevbpf [this message]
2023-08-28 20:00 ` patchwork-bot+netdevbpf
2023-08-29 12:38 ` Alexander Stein
2023-08-29 12:38 ` Alexander Stein
2023-08-29 13:10 ` Russell King (Oracle)
2023-08-29 13:10 ` Russell King (Oracle)
2023-08-29 13:20 ` Alexander Stein
2023-08-29 13:20 ` Alexander Stein
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=169325282356.23387.6771304913662801847.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chenfeiyang@loongson.cn \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=festevam@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=jernej.skrabec@gmail.com \
--cc=joabreu@synopsys.com \
--cc=kernel@esmil.dk \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=matthias.bgg@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=s.hauer@pengutronix.de \
--cc=samin.guo@starfivetech.com \
--cc=samuel@sholland.org \
--cc=shawnguo@kernel.org \
--cc=vz@mleia.com \
--cc=wens@csie.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 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.