From: patchwork-bot+netdevbpf@kernel.org
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: davem@davemloft.net, kuba@kernel.org, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, netdev@vger.kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/5] net: dsa: Allow default tag protocol to be overridden from DT
Date: Wed, 21 Apr 2021 00:00:10 +0000 [thread overview]
Message-ID: <161896321086.2554.15712504527093585485.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210420185311.899183-1-tobias@waldekranz.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 20 Apr 2021 20:53:06 +0200 you wrote:
> This is a continuation of the work started in this patch:
> https://lore.kernel.org/netdev/20210323102326.3677940-1-tobias@waldekranz.com/
>
> In addition to the mv88e6xxx support to dynamically change the
> protocol, it is now possible to override the protocol from the device
> tree. This means that when a board vendor finds an incompatibility,
> they can specify a working protocol in the DT, and users will not have
> to worry about it.
>
> [...]
Here is the summary with links:
- [v3,net-next,1/5] net: dsa: mv88e6xxx: Mark chips with undocumented EDSA tag support
https://git.kernel.org/netdev/net-next/c/670bb80f8196
- [v3,net-next,2/5] net: dsa: mv88e6xxx: Allow dynamic reconfiguration of tag protocol
https://git.kernel.org/netdev/net-next/c/9a99bef5f87f
- [v3,net-next,3/5] net: dsa: Only notify CPU ports of changes to the tag protocol
https://git.kernel.org/netdev/net-next/c/21e0b508c8d1
- [v3,net-next,4/5] net: dsa: Allow default tag protocol to be overridden from DT
https://git.kernel.org/netdev/net-next/c/deff710703d8
- [v3,net-next,5/5] dt-bindings: net: dsa: Document dsa-tag-protocol property
https://git.kernel.org/netdev/net-next/c/eb78cacebaf2
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-04-21 0:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 18:53 [PATCH v3 net-next 0/5] net: dsa: Allow default tag protocol to be overridden from DT Tobias Waldekranz
2021-04-20 18:53 ` [PATCH v3 net-next 1/5] net: dsa: mv88e6xxx: Mark chips with undocumented EDSA tag support Tobias Waldekranz
2021-04-20 18:53 ` [PATCH v3 net-next 2/5] net: dsa: mv88e6xxx: Allow dynamic reconfiguration of tag protocol Tobias Waldekranz
2021-04-20 18:53 ` [PATCH v3 net-next 3/5] net: dsa: Only notify CPU ports of changes to the " Tobias Waldekranz
2021-04-20 18:53 ` [PATCH v3 net-next 4/5] net: dsa: Allow default tag protocol to be overridden from DT Tobias Waldekranz
2021-04-20 23:16 ` Vladimir Oltean
2021-04-20 18:53 ` [PATCH v3 net-next 5/5] dt-bindings: net: dsa: Document dsa-tag-protocol property Tobias Waldekranz
2021-04-21 0: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=161896321086.2554.15712504527093585485.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tobias@waldekranz.com \
--cc=vivien.didelot@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 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).