From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <olteanv@gmail.com>
Cc: f.fainelli@gmail.com, davem@davemloft.net, kuba@kernel.org,
netdev@vger.kernel.org, andrew@lunn.ch, vivien.didelot@gmail.com,
bcm-kernel-feedback-list@broadcom.com, zajec5@gmail.com
Subject: Re: [PATCH v2 net-next 0/4] Reduce coupling between DSA and Broadcom SYSTEMPORT driver
Date: Thu, 07 Jan 2021 23:50:11 +0000 [thread overview]
Message-ID: <161006341112.8293.6610475069406469009.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210107012403.1521114-1-olteanv@gmail.com>
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@nxp.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
prev parent reply other threads:[~2021-01-07 23:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 1:23 [PATCH v2 net-next 0/4] Reduce coupling between DSA and Broadcom SYSTEMPORT driver Vladimir Oltean
2021-01-07 1:24 ` [PATCH v2 net-next 1/4] net: dsa: move the Broadcom tag information in a separate header file Vladimir Oltean
2021-01-07 1:24 ` [PATCH v2 net-next 2/4] net: dsa: export dsa_slave_dev_check Vladimir Oltean
2021-01-07 1:24 ` [PATCH v2 net-next 3/4] net: systemport: use standard netdevice notifier to detect DSA presence Vladimir Oltean
2021-01-07 1:24 ` [PATCH v2 net-next 4/4] net: dsa: remove the DSA specific notifiers Vladimir Oltean
2021-01-07 23:50 ` 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=161006341112.8293.6610475069406469009.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@gmail.com \
--cc=zajec5@gmail.com \
/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.