From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Machon <daniel.machon@microchip.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, lars.povlsen@microchip.com,
Steen.Hegelund@microchip.com, UNGLinuxDriver@microchip.com,
joe@perches.com, error27@gmail.com, horatiu.vultur@microchip.com,
Julia.Lawall@inria.fr, petrm@nvidia.com, vladimir.oltean@nxp.com,
maxime.chevallier@bootlin.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/6] Introduce new DCB rewrite table
Date: Fri, 20 Jan 2023 12:30:20 +0000 [thread overview]
Message-ID: <167421782096.21057.3566863729140483303.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230118210830.2287069-1-daniel.machon@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 18 Jan 2023 22:08:24 +0100 you wrote:
> There is currently no support for per-port egress mapping of priority to PCP and
> priority to DSCP. Some support for expressing egress mapping of PCP is supported
> through ip link, with the 'egress-qos-map', however this command only maps
> priority to PCP, and for vlan interfaces only. DCB APP already has support for
> per-port ingress mapping of PCP/DEI, DSCP and a bunch of other stuff. So why not
> take advantage of this fact, and add a new table that does the reverse.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/6] net: dcb: modify dcb_app_add to take list_head ptr as parameter
https://git.kernel.org/netdev/net-next/c/34b7074d3fba
- [net-next,v3,2/6] net: dcb: add new common function for set/del of app/rewr entries
https://git.kernel.org/netdev/net-next/c/30568334b657
- [net-next,v3,3/6] net: dcb: add new rewrite table
https://git.kernel.org/netdev/net-next/c/622f1b2fae2e
- [net-next,v3,4/6] net: dcb: add helper functions to retrieve PCP and DSCP rewrite maps
https://git.kernel.org/netdev/net-next/c/1df99338e6d4
- [net-next,v3,5/6] net: microchip: sparx5: add support for PCP rewrite
https://git.kernel.org/netdev/net-next/c/2234879f4ca1
- [net-next,v3,6/6] net: microchip: sparx5: add support for DSCP rewrite
https://git.kernel.org/netdev/net-next/c/246c77f666b4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-01-20 12:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 21:08 [PATCH net-next v3 0/6] Introduce new DCB rewrite table Daniel Machon
2023-01-18 21:08 ` [PATCH net-next v3 1/6] net: dcb: modify dcb_app_add to take list_head ptr as parameter Daniel Machon
2023-01-19 9:22 ` Petr Machata
2023-01-18 21:08 ` [PATCH net-next v3 2/6] net: dcb: add new common function for set/del of app/rewr entries Daniel Machon
2023-01-19 9:21 ` Petr Machata
2023-01-18 21:08 ` [PATCH net-next v3 3/6] net: dcb: add new rewrite table Daniel Machon
2023-01-19 8:59 ` Petr Machata
2023-01-18 21:08 ` [PATCH net-next v3 4/6] net: dcb: add helper functions to retrieve PCP and DSCP rewrite maps Daniel Machon
2023-01-19 9:23 ` Petr Machata
2023-01-18 21:08 ` [PATCH net-next v3 5/6] net: microchip: sparx5: add support for PCP rewrite Daniel Machon
2023-01-18 21:08 ` [PATCH net-next v3 6/6] net: microchip: sparx5: add support for DSCP rewrite Daniel Machon
2023-01-20 12: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=167421782096.21057.3566863729140483303.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Julia.Lawall@inria.fr \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=error27@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=joe@perches.com \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=vladimir.oltean@nxp.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).