From: patchwork-bot+netdevbpf@kernel.org <patchwork-bot+netdevbpf@kernel.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH net-next v3 0/2] net: ftgmac100: support fixed link
Date: Thu, 15 Sep 2022 11:00:17 +0000 [thread overview]
Message-ID: <166323961746.5581.16008979446604456337.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220907054453.20016-1-rentao.bupt@gmail.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 6 Sep 2022 22:44:51 -0700 you wrote:
> From: Tao Ren <rentao.bupt@gmail.com>
>
> The patch series adds fixed link support to ftgmac100 driver.
>
> Patch #1 adds fixed link logic into ftgmac100 driver.
>
> Patch #2 enables mac3 controller in Elbert dts: Elbert mac3 is connected
> to the onboard switch BCM53134P's IMP_RGMII port directly (no PHY
> between BMC MAC and BCM53134P).
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] net: ftgmac100: support fixed link
https://git.kernel.org/netdev/net-next/c/38561ded50d0
- [net-next,v3,2/2] ARM: dts: aspeed: elbert: Enable mac3 controller
https://git.kernel.org/netdev/net-next/c/ce6ce9176975
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:[~2022-09-15 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 5:44 [PATCH net-next v3 0/2] net: ftgmac100: support fixed link rentao.bupt
2022-09-07 5:44 ` [PATCH net-next v3 1/2] " rentao.bupt
2022-09-07 18:43 ` Florian Fainelli
2022-09-07 5:44 ` [PATCH net-next v3 2/2] ARM: dts: aspeed: elbert: Enable mac3 controller rentao.bupt
2022-09-07 18:31 ` Andrew Lunn
2022-09-07 18:44 ` Florian Fainelli
2022-09-15 11: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=166323961746.5581.16008979446604456337.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=linux-aspeed@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).