[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALs4sv2gUisgf4QxO3Sed4y7TSo3tnieVSen6yGSPSgHh9xT7w@mail.gmail.com>
Date: Tue, 23 Sep 2025 17:49:50 +0530
From: Pavan Chebbi <pavan.chebbi@...adcom.com>
To: Jonathan Cameron <jonathan.cameron@...wei.com>
Cc: jgg@...pe.ca, michael.chan@...adcom.com, dave.jiang@...el.com,
saeedm@...dia.com, davem@...emloft.net, corbet@....net, edumazet@...gle.com,
gospo@...adcom.com, kuba@...nel.org, netdev@...r.kernel.org,
pabeni@...hat.com, andrew+netdev@...n.ch, selvin.xavier@...adcom.com,
leon@...nel.org, kalesh-anakkur.purayil@...adcom.com
Subject: Re: [PATCH net-next v2 5/6] bnxt_fwctl: Add bnxt fwctl device
On Tue, Sep 23, 2025 at 4:47 PM Jonathan Cameron
<jonathan.cameron@...wei.com> wrote:
>
> I was kind of expecting something called validate_rpc to do
> the scope checks that we see in other drivers.
> e.g. mlx5ctl_validate_rpc()
>
Right, skipped applying scope with the intention to support all the commands,
assuming good faith in the sender. Thanks for your comment, I realize besides
missing to implement an important fwctl construct, it also does make me appear
lazy, to segregate commands from a really large list. But I will do it in v3.
Thanks for pointing out.
Powered by blists - more mailing lists