From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
alazar@nvidia.com, cjubran@nvidia.com, gal@nvidia.com,
kees@kernel.org, linux-kernel@vger.kernel.org,
oss-drivers@corigine.com, horms@kernel.org
Subject: Re: [PATCH net-next V2] net/dcb: Validate bandwidth for non-ETS traffic classes
Date: Tue, 20 Oct 2026 01:30:09 +0000 [thread overview]
Message-ID: <179245980903.3422113.4762636508765499257.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261011083929.739261-1-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 11 Oct 2026 11:39:29 +0300 you wrote:
> From: Alexei Lazar <alazar@nvidia.com>
>
> The IEEE 802.1Qaz standard defines that bandwidth allocation percentages
> only apply to ETS traffic classes. Reject ETS configurations that
> specify non-zero bandwidth for non-ETS traffic classes.
>
> Placing this check in dcbnl_ieee_set() enforces the constraint uniformly
> for all drivers rather than relying on each driver to validate it
> independently.
>
> [...]
Here is the summary with links:
- [net-next,V2] net/dcb: Validate bandwidth for non-ETS traffic classes
https://git.kernel.org/netdev/net-next/c/0e36a335c84e
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:[~2026-10-20 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 8:39 Tariq Toukan
2026-10-12 8:40 ` netdev-bot+sashiko
2026-10-20 1: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=179245980903.3422113.4762636508765499257.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alazar@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=tariqt@nvidia.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
all inboxes | Powered by JetHome®