From: Jakub Kicinski <kuba@kernel.org>
To: netdev-bot+sashiko@kernel.org
Cc: tariqt@nvidia.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
alazar@nvidia.com, cjubran@nvidia.com, dtatulea@nvidia.com,
gal@nvidia.com, leon@kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, mbloch@nvidia.com, saeedm@nvidia.com
Subject: Re: [PATCH net-next 1/2] net/mlx5e: Select DCBX HOST/AUTO from capability flags in setdcbx
Date: Mon, 19 Oct 2026 18:20:54 -0700 [thread overview]
Message-ID: <20261019182054.7ea49d39@kernel.org> (raw)
In-Reply-To: <179180701752.434549.16734295951082648234@kernel.org>
On Mon, 12 Oct 2026 12:10:17 +0000 netdev-bot+sashiko@kernel.org wrote:
> - [Medium] mlx5e_dcbnl_setdcbx()
> (drivers/net/ethernet/mellanox/mlx5/core/en_dcbnl.c) now returns…
> - [Medium] The patch reports firmware AUTO mode as CEE|IEEE|LLD_MANAGED
> (0x0e), but only on the setdcbx HOST->AUTO transition path.
These look at the very least plausible, I'm assuming the lack of
dismissal/response means v2 is coming.
--
pw-bot: cr
next prev parent reply other threads:[~2026-10-20 1:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 11:28 [PATCH net-next 0/2] net/mlx5e: Align setdcbx with DCBX capability flags Tariq Toukan
2026-10-11 11:28 ` [PATCH net-next 1/2] net/mlx5e: Select DCBX HOST/AUTO from capability flags in setdcbx Tariq Toukan
2026-10-12 11:29 ` sashiko-bot
2026-10-12 12:10 ` netdev-bot+sashiko
2026-10-20 1:20 ` Jakub Kicinski [this message]
2026-10-11 11:29 ` [PATCH net-next 2/2] net/mlx5e: Add DCB_CAP_DCBX_LLD_MANAGED support " Tariq Toukan
2026-10-12 11:29 ` sashiko-bot
2026-10-12 12:10 ` netdev-bot+sashiko
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=20261019182054.7ea49d39@kernel.org \
--to=kuba@kernel.org \
--cc=alazar@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@kernel.org \
--cc=gal@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.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 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.