Subject: Re: [RFT net-next 1/6] devlink: expose instance locking and add locked port registering

From: Jiri Pirko <[email-masked]>
Date: Mon, 14 Mar 2022 13:43:36 +0100

Fri, Mar 11, 2022 at 05:33:32PM CET, [email-masked] wrote:
>On Fri, 11 Mar 2022 10:15:30 +0100 Jiri Pirko wrote:
>>> The goal is for that API to be the main one, we can rename the devlink_
>>> to something else at the end. The parts of it which are not completely
>>> removed.  
>> 
>> Okay. So please have it as:
>> devl_* - normal
>> __devl_* - unlocked
>
>Isn't it fairly awkward for the main intended API to have __ in the
>name? __ means unsafe / make sure you know what you're doing.
>
>There's little room for confusion here, we have locking asserts
>everywhere.

Well, I think it is common to have "__" prefixed for unlocked variant.
Idk.