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, Steen.Hegelund@microchip.com,
UNGLinuxDriver@microchip.com, casper.casan@gmail.com,
horatiu.vultur@microchip.com, rmk+kernel@armlinux.org.uk,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net-next v2 0/5] Add QoS offload support for sparx5
Date: Fri, 23 Sep 2022 09:20:16 +0000 [thread overview]
Message-ID: <166392481624.15254.1338546530470864801.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220920101432.139323-1-daniel.machon@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 20 Sep 2022 12:14:27 +0200 you wrote:
> This patch series adds support for offloading QoS features with the tc
> command suite, to the sparx5 switch. The new offloadable QoS features
> introduced in this patch series are:
>
> - tc-mqprio for mapping traffic class to hardware queue. Queues are by
> default mapped 1:1 in hardware, as such the mqprio qdisc is used as
> an attachment point for qdiscs tbf and ets.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/5] net: microchip: sparx5: add tc setup hook
https://git.kernel.org/netdev/net-next/c/65ec1bbe0297
- [net-next,v2,2/5] net: microchip: sparx5: add support for offloading mqprio qdisc
https://git.kernel.org/netdev/net-next/c/ab0e493e75bd
- [net-next,v2,3/5] net: microchip: sparx5: add support for offloading tbf qdisc
https://git.kernel.org/netdev/net-next/c/e02a5ac6bf77
- [net-next,v2,4/5] net: microchip: sparx5: add support for offloading ets qdisc
https://git.kernel.org/netdev/net-next/c/211225428d65
- [net-next,v2,5/5] maintainers: update MAINTAINERS file.
https://git.kernel.org/netdev/net-next/c/d91a6d049010
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:[~2022-09-23 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 10:14 [PATCH net-next v2 0/5] Add QoS offload support for sparx5 Daniel Machon
2022-09-20 10:14 ` [PATCH net-next v2 1/5] net: microchip: sparx5: add tc setup hook Daniel Machon
2022-09-20 10:14 ` [PATCH net-next v2 2/5] net: microchip: sparx5: add support for offloading mqprio qdisc Daniel Machon
2022-09-20 10:14 ` [PATCH net-next v2 3/5] net: microchip: sparx5: add support for offloading tbf qdisc Daniel Machon
2022-09-20 10:14 ` [PATCH net-next v2 4/5] net: microchip: sparx5: add support for offloading ets qdisc Daniel Machon
2022-09-20 10:14 ` [PATCH net-next v2 5/5] maintainers: update MAINTAINERS file Daniel Machon
2022-09-23 9:20 ` 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=166392481624.15254.1338546530470864801.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=casper.casan@gmail.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
/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).