From: Kohei Enju <enjuk@amazon.com>
To: <dsahern@kernel.org>
Cc: <aleksandr.loktionov@intel.com>, <andrew+netdev@lunn.ch>,
<anthony.l.nguyen@intel.com>, <daniel.zahka@gmail.com>,
<davem@davemloft.net>, <david.m.ertman@intel.com>,
<edumazet@google.com>, <intel-wired-lan@lists.osuosl.org>,
<kuba@kernel.org>, <michal.swiatkowski@linux.intel.com>,
<mustafa.ismail@intel.com>, <netdev@vger.kernel.org>,
<nikolay@nvidia.com>, <pabeni@redhat.com>,
<paul.greenwalt@intel.com>, <przemyslaw.kitszel@intel.com>,
<shiraz.saleem@intel.com>, <tatyana.e.nikolova@intel.com>
Subject: Re: [PATCH net] drivers: net: ice: fix devlink parameters get without irdma
Date: Mon, 23 Feb 2026 04:20:11 +0900 [thread overview]
Message-ID: <20260222192011.1147-1-enjuk@amazon.com> (raw)
In-Reply-To: <56e04cb1-e205-4076-8236-1f172a75793d@kernel.org>
On Sun, 22 Feb 2026 11:27:30 -0700, David Ahern wrote:
> On 2/13/26 1:48 AM, Nikolay Aleksandrov wrote:
> > If CONFIG_IRDMA isn't enabled but there are ice NICs in the system, the
> > driver will prevent full devlink dev param show dump because its rdma get
> > callbacks return ENODEV and stop the dump. For example:
> > $ devlink dev param show
> > pci/0000:82:00.0:
> > name msix_vec_per_pf_max type generic
> > values:
> > cmode driverinit value 2
> > name msix_vec_per_pf_min type generic
> > values:
> > cmode driverinit value 2
> > kernel answers: No such device
> >
> > Returning EOPNOTSUPP allows the dump to continue so we can see all devices'
> > devlink parameters.
> >
> > Fixes: c24a65b6a27c ("iidc/ice/irdma: Update IDC to support multiple consumers")
> > Signed-off-by: Nikolay Aleksandrov <nikolay@nvidia.com>
> > ---
> > drivers/net/ethernet/intel/ice/devlink/devlink.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
>
> This patch was marked as awaiting upstream; I wanted to confirm it is in
> Intel's queue or was the expectation for netdev maintainer's to pick it up?
I see it's in Intel's queue.
https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue.git/log/?h=dev-queue
next prev parent reply other threads:[~2026-02-22 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 8:48 [PATCH net] drivers: net: ice: fix devlink parameters get without irdma Nikolay Aleksandrov
2026-02-13 9:15 ` Loktionov, Aleksandr
2026-02-13 10:37 ` Przemek Kitszel
2026-02-22 18:27 ` David Ahern
2026-02-22 19:20 ` Kohei Enju [this message]
2026-03-06 10:05 ` [Intel-wired-lan] " Rinitha, SX
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=20260222192011.1147-1-enjuk@amazon.com \
--to=enjuk@amazon.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=daniel.zahka@gmail.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=michal.swiatkowski@linux.intel.com \
--cc=mustafa.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=pabeni@redhat.com \
--cc=paul.greenwalt@intel.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=shiraz.saleem@intel.com \
--cc=tatyana.e.nikolova@intel.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