[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALs4sv2ApzFgkst-bMk1Wx2TVf4r38Em6LsJbFuvY5O6_0wBiw@mail.gmail.com>
Date: Tue, 23 Sep 2025 17:51:19 +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 3/6] bnxt_en: Make a lookup table for
supported aux bus devices
On Tue, Sep 23, 2025 at 4:19 PM Jonathan Cameron
<jonathan.cameron@...wei.com> wrote:
>
> On Tue, 23 Sep 2025 02:58:22 -0700
> Pavan Chebbi <pavan.chebbi@...adcom.com> wrote:
>
> > We could maintain a look up table of aux bus devices supported
> > by bnxt. This way, the aux bus init/add/uninit/del could have
> > generic code to work on any of bnxt's aux devices.
> >
> > Reviewed-by: Andy Gospodarek <gospo@...adcom.com>
> > Signed-off-by: Pavan Chebbi <pavan.chebbi@...adcom.com>
>
> Ah. Ok. This does make it more generic. Smash this and patch 2 together
> so we don't have the intermediate state where stuff is partly generic.
>
Hi Jonathan, thanks for the review. Right, I assumed context while
preparing the patches.
I will address this patch break-up and other comments in v3. Thanks again.
Powered by blists - more mailing lists