From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, mlxsw@nvidia.com, saeedm@nvidia.com,
moshe@nvidia.com
Subject: Re: [patch net-next 3/3] net: devlink: fix unlocked vs locked functions descriptions
Date: Fri, 1 Jul 2022 18:35:21 +0200 [thread overview]
Message-ID: <Yr8iSRZEMSdhOGCQ@nanopsycho> (raw)
In-Reply-To: <20220701093037.36ae3c67@kernel.org>
Fri, Jul 01, 2022 at 06:30:37PM CEST, kuba@kernel.org wrote:
>On Fri, 1 Jul 2022 11:59:26 +0200 Jiri Pirko wrote:
>
>> + * Register devlink port with provided port index. User can use
>> + * any indexing, even hw-related one. devlink_port structure
>> + * is convenient to be embedded inside user driver private structure.
>> + * Note that the caller should take care of zeroing the devlink_port
>> + * structure.
>
>Should we also mention that the port type has to be set later?
>I guess that may be beyond the scope.
Let's do that in a separate patch. This is just to keep consistency
between devlink_ and devl_
>
>> + */
>
>> +/**
>> + * devlink_port_unregister - Unregister devlink port
>
>devl_
Right.
>
>> + *
>> + * @devlink_port: devlink port
>> + */
>
>I wonder if we should use this as an opportunity to start following
>the more modern kdoc format:
>
>No tab indentation, and () after the function's name.
>
>At least for the new kdoc we add.
Okay. Makes sense.
>
>> void devl_port_unregister(struct devlink_port *devlink_port)
>> {
>> lockdep_assert_held(&devlink_port->devlink->lock);
>
prev parent reply other threads:[~2022-07-01 16:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 9:59 [patch net-next 0/3] net: devlink: devl_* cosmetic fixes Jiri Pirko
2022-07-01 9:59 ` [patch net-next 1/3] net: devlink: move unlocked function prototypes alongside the locked ones Jiri Pirko
2022-07-01 9:59 ` [patch net-next 2/3] net: devlink: call lockdep_assert_held() for devlink->lock directly Jiri Pirko
2022-07-01 16:33 ` Jakub Kicinski
2022-07-02 15:58 ` Jiri Pirko
2022-07-02 19:29 ` Jakub Kicinski
2022-07-04 6:19 ` Jiri Pirko
2022-07-05 2:58 ` Jakub Kicinski
2022-07-07 8:04 ` Jiri Pirko
2022-07-01 9:59 ` [patch net-next 3/3] net: devlink: fix unlocked vs locked functions descriptions Jiri Pirko
2022-07-01 16:30 ` Jakub Kicinski
2022-07-01 16:35 ` Jiri Pirko [this message]
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=Yr8iSRZEMSdhOGCQ@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).