From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, leonro@nvidia.com,
jiri@nvidia.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, saeedm@nvidia.com
Subject: Re: [PATCH net-next] devlink: Simplify devlink port API calls
Date: Sun, 08 Aug 2021 12:00:06 +0000 [thread overview]
Message-ID: <162842400618.17847.5783406967029624966.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <c9f15f122181f05f09fffd2380365b9925dd6427.1628422645.git.leonro@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Sun, 8 Aug 2021 14:41:21 +0300 you wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Devlink port already has pointer to the devlink instance and all API
> calls that forward these devlink ports to the drivers perform same
> "devlink_port->devlink" assignment before actual call.
>
> This patch removes useless parameter and allows us in the future
> to create specific devlink_port_ops to manage user space access with
> reliable ops assignment.
>
> [...]
Here is the summary with links:
- [net-next] devlink: Simplify devlink port API calls
https://git.kernel.org/netdev/net-next/c/82564f6c706a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-08-08 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 11:41 [PATCH net-next] devlink: Simplify devlink port API calls Leon Romanovsky
2021-08-08 12:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-09 8:21 kernel test robot
2021-08-09 10:54 ` kernel test robot
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=162842400618.17847.5783406967029624966.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.