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 0/3] net: devlink: couple of trivial fixes
Date: Wed, 13 Jul 2022 16:03:17 +0200 [thread overview]
Message-ID: <Ys7QpWEVIh7NfrAx@nanopsycho> (raw)
In-Reply-To: <20220712104853.2831646-1-jiri@resnulli.us>
Guys, this is incorrectly marked as "Changes Requested" in patchwork,
however I got ack from Jakub and no changes were requested.
Could you apply, or should I re-send?
Thanks!
Tue, Jul 12, 2022 at 12:48:50PM CEST, jiri@resnulli.us wrote:
>From: Jiri Pirko <jiri@nvidia.com>
>
>Just a couple of trivial fixes I found on the way.
>
>Jiri Pirko (3):
> net: devlink: make devlink_dpipe_headers_register() return void
> net: devlink: fix a typo in function name devlink_port_new_notifiy()
> net: devlink: fix return statement in devlink_port_new_notify()
>
> .../net/ethernet/mellanox/mlxsw/spectrum_dpipe.c | 6 ++----
> include/net/devlink.h | 2 +-
> net/core/devlink.c | 16 +++++++---------
> 3 files changed, 10 insertions(+), 14 deletions(-)
>
>--
>2.35.3
>
next prev parent reply other threads:[~2022-07-13 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 10:48 [patch net-next 0/3] net: devlink: couple of trivial fixes Jiri Pirko
2022-07-12 10:48 ` [patch net-next 1/3] net: devlink: make devlink_dpipe_headers_register() return void Jiri Pirko
2022-07-12 10:48 ` [patch net-next 2/3] net: devlink: fix a typo in function name devlink_port_new_notifiy() Jiri Pirko
2022-07-12 10:48 ` [patch net-next 3/3] net: devlink: fix return statement in devlink_port_new_notify() Jiri Pirko
2022-07-13 1:45 ` [patch net-next 0/3] net: devlink: couple of trivial fixes Jakub Kicinski
2022-07-13 14:03 ` Jiri Pirko [this message]
2022-07-13 14:17 ` 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=Ys7QpWEVIh7NfrAx@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).