From: Jakub Kicinski <kuba@kernel•org>
To: Leon Romanovsky <leon@kernel•org>
Cc: Eric Joyner <eric.joyner@amd•com>,
netdev@vger•kernel.org, linux-rdma@vger•kernel.org,
Brett Creeley <brett.creeley@amd•com>,
Andrew Lunn <andrew+netdev@lunn•ch>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Paolo Abeni <pabeni@redhat•com>,
Abhijit Gangurde <abhijit.gangurde@amd•com>,
Allen Hubbe <allen.hubbe@amd•com>, Jason Gunthorpe <jgg@ziepe•ca>,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>
Subject: Re: [PATCH net-next 3/4] RDMA/ionic: Add debugfs support
Date: Wed, 13 May 2026 17:23:14 -0700 [thread overview]
Message-ID: <20260513172314.35e71e7b@kernel.org> (raw)
In-Reply-To: <20260513072113.GE15586@unreal>
On Wed, 13 May 2026 10:21:13 +0300 Leon Romanovsky wrote:
> 3. The patch is too large and exposes too many details that should be
> gathered through the FW (fwctl).
Why? What's wrong with debugfs? Much easier for people to access.
next prev parent reply other threads:[~2026-05-14 0:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 4:19 [PATCH net-next 0/4] RDMA/net/ionic: Misc updates Eric Joyner
2026-05-06 4:19 ` [PATCH net-next 1/4] RDMA/ionic: Update copyright year to 2026 Eric Joyner
2026-05-06 4:19 ` [PATCH net-next 2/4] net/ionic: Add devlink parameter for RDMA Eric Joyner
2026-05-06 4:19 ` [PATCH net-next 3/4] RDMA/ionic: Add debugfs support Eric Joyner
2026-05-13 7:21 ` Leon Romanovsky
2026-05-14 0:23 ` Jakub Kicinski [this message]
2026-05-14 6:00 ` Leon Romanovsky
2026-05-14 7:04 ` Greg Kroah-Hartman
2026-05-14 16:35 ` Leon Romanovsky
2026-05-06 4:19 ` [PATCH net-next 4/4] RDMA/ionic: Add DCQCN parameter configuration via debugfs Eric Joyner
2026-05-06 22:59 ` [PATCH net-next 0/4] RDMA/net/ionic: Misc updates Jakub Kicinski
2026-05-14 14:33 ` Abhijit Gangurde
2026-05-14 16:40 ` Leon Romanovsky
2026-05-14 17:19 ` Creeley, Brett
2026-05-17 14:55 ` Leon Romanovsky
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=20260513172314.35e71e7b@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=abhijit.gangurde@amd$(echo .)com \
--cc=allen.hubbe@amd$(echo .)com \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=brett.creeley@amd$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=eric.joyner@amd$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=jgg@ziepe$(echo .)ca \
--cc=leon@kernel$(echo .)org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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