[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <161006341112.8293.6610475069406469009.git-patchwork-notify@kernel.org>
Date: Thu, 07 Jan 2021 23:50:11 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Vladimir Oltean <olteanv@...il.com>
Cc: f.fainelli@...il.com, davem@...emloft.net, kuba@...nel.org,
netdev@...r.kernel.org, andrew@...n.ch, vivien.didelot@...il.com,
bcm-kernel-feedback-list@...adcom.com, zajec5@...il.com
Subject: Re: [PATCH v2 net-next 0/4] Reduce coupling between DSA and Broadcom
SYSTEMPORT driver
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Thu, 7 Jan 2021 03:23:59 +0200 you wrote:
> From: Vladimir Oltean <vladimir.oltean@....com>
>
> Upon a quick inspection, it seems that there is some code in the generic
> DSA layer that is somehow specific to the Broadcom SYSTEMPORT driver.
> The challenge there is that the hardware integration is very tight between
> the switch and the DSA master interface. However this does not mean that
> the drivers must also be as integrated as the hardware is. We can avoid
> creating a DSA notifier just for the Broadcom SYSTEMPORT, and we can
> move some Broadcom-specific queue mapping helpers outside of the common
> include/net/dsa.h.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/4] net: dsa: move the Broadcom tag information in a separate header file
https://git.kernel.org/netdev/net-next/c/f46b9b8ee89b
- [v2,net-next,2/4] net: dsa: export dsa_slave_dev_check
https://git.kernel.org/netdev/net-next/c/a5e3c9ba9258
- [v2,net-next,3/4] net: systemport: use standard netdevice notifier to detect DSA presence
https://git.kernel.org/netdev/net-next/c/1593cd40d785
- [v2,net-next,4/4] net: dsa: remove the DSA specific notifiers
https://git.kernel.org/netdev/net-next/c/1dbb130281c4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists