From: patchwork-bot+netdevbpf@kernel•org
To: Russell King (Oracle) <linux@armlinux•org.uk>
Cc: andrew@lunn•ch, vivien.didelot@gmail•com, kabel@kernel•org,
davem@davemloft•net, edumazet@google•com, f.fainelli@gmail•com,
kuba@kernel•org, netdev@vger•kernel.org, pabeni@redhat•com,
olteanv@gmail•com
Subject: Re: [PATCH net-next 0/2] net: dsa: mv88e6xxx: get rid of SPEED_MAX
Date: Fri, 24 Jun 2022 03:30:13 +0000 [thread overview]
Message-ID: <165604141371.13504.3415106547554041008.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <YrGQBssOvQBZiDS4@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Tue, 21 Jun 2022 10:31:50 +0100 you wrote:
> Hi,
>
> This series does two things:
>
> 1. it gets rid of mv88e6065_port_set_speed_duplex() which is completely
> unused (do we support this device? I couldn't find it in the tables
> in chip.c) This has a max speed of 200Mbps which we don't support.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: dsa: mv88e6xxx: remove mv88e6065 dead code
https://git.kernel.org/netdev/net-next/c/aa64bc1990b2
- [net-next,2/2] net: dsa: mv88e6xxx: get rid of SPEED_MAX setting
https://git.kernel.org/netdev/net-next/c/3c783b83bd0f
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-06-24 3:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 9:31 [PATCH net-next 0/2] net: dsa: mv88e6xxx: get rid of SPEED_MAX Russell King (Oracle)
2022-06-21 9:37 ` [PATCH net-next 1/2] net: dsa: mv88e6xxx: remove mv88e6065 dead code Russell King (Oracle)
2022-06-21 9:37 ` [PATCH net-next 2/2] net: dsa: mv88e6xxx: get rid of SPEED_MAX setting Russell King
2022-06-24 3:30 ` 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=165604141371.13504.3415106547554041008.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=f.fainelli@gmail$(echo .)com \
--cc=kabel@kernel$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=netdev@vger$(echo .)kernel.org \
--cc=olteanv@gmail$(echo .)com \
--cc=pabeni@redhat$(echo .)com \
--cc=vivien.didelot@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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