From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, mlxsw@nvidia.com, saeedm@nvidia.com,
moshe@nvidia.com
Subject: Re: [patch net-next v3/repost 0/3] net: devlink: devl_* cosmetic fixes
Date: Mon, 11 Jul 2022 16:31:56 +0200 [thread overview]
Message-ID: <Ysw0XA2NC3cGxWIY@nanopsycho> (raw)
In-Reply-To: <20220711132607.2654337-1-jiri@resnulli.us>
Jakub, this will probably conflict with Saeeds PR. Let me know and I
will rebase. Thanks!
Mon, Jul 11, 2022 at 03:26:04PM CEST, jiri@resnulli.us wrote:
>From: Jiri Pirko <jiri@nvidia.com>
>
>Hi. This patches just fixes some small cosmetic issues of devl_* related
>functions which I found on the way.
>
>Jiri Pirko (3):
> net: devlink: fix unlocked vs locked functions descriptions
> net: devlink: use helpers to work with devlink->lock mutex
> net: devlink: move unlocked function prototypes alongside the locked
> ones
>
> include/net/devlink.h | 16 ++-
> net/core/devlink.c | 284 ++++++++++++++++++++++++------------------
> 2 files changed, 167 insertions(+), 133 deletions(-)
>
>--
>2.35.3
>
next prev parent reply other threads:[~2022-07-11 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 13:26 [patch net-next v3/repost 0/3] net: devlink: devl_* cosmetic fixes Jiri Pirko
2022-07-11 13:26 ` [patch net-next v3/repost 1/3] net: devlink: fix unlocked vs locked functions descriptions Jiri Pirko
2022-07-11 13:26 ` [patch net-next v3/repost 2/3] net: devlink: use helpers to work with devlink->lock mutex Jiri Pirko
2022-07-11 13:26 ` [patch net-next v3/repost 3/3] net: devlink: move unlocked function prototypes alongside the locked ones Jiri Pirko
2022-07-11 14:31 ` Jiri Pirko [this message]
2022-07-12 8:53 ` [patch net-next v3/repost 0/3] net: devlink: devl_* cosmetic fixes Paolo Abeni
2022-07-12 10:04 ` Jiri Pirko
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=Ysw0XA2NC3cGxWIY@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