[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a66vxut9.fsf@nvidia.com>
Date: Mon, 19 Sep 2022 17:11:33 +0200
From: Petr Machata <petrm@...dia.com>
To: <Daniel.Machon@...rochip.com>
CC: <petrm@...dia.com>, <netdev@...r.kernel.org>,
<Allan.Nielsen@...rochip.com>, <UNGLinuxDriver@...rochip.com>,
<maxime.chevallier@...tlin.com>, <vladimir.oltean@....com>,
<kuba@...nel.org>, <vinicius.gomes@...el.com>,
<thomas.petazzoni@...tlin.com>
Subject: Re: [RFC PATCH v2 net-next 0/2] Add PCP selector and new APPTRUST
attribute
<Daniel.Machon@...rochip.com> writes:
> Den Mon, Sep 19, 2022 at 09:54:23AM +0200 skrev Petr Machata:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> Thanks, this looks good to me overall, despite the several points
>> Vladimir and I raised. I think it would be good to send this as non-RFC.
>>
>> Note that for the non-RFC version, an actual user of the interface needs
>> to be present as well. So one of the offloading drivers should be
>> adapted to make use of the APP_TRUST and the new PCP selector.
>> mlxsw would like to make use of both, but I don't know when I will have
>> time to implement that.
>
> Sounds good, and thanks for reviewing to you both.
> I will go ahead and add support for this in the sparx5 driver - most of it
> is already implemented during the tests anyway.
>
> Should the driver support be posted together with said non-RFC patch
> series?
Yes.
Powered by blists - more mailing lists