From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, saeedm@nvidia.com, netdev@vger.kernel.org,
leonro@nvidia.com
Subject: Re: [PATCH net-next] net/mlx5: remove the recent devlink params
Date: Tue, 26 Oct 2021 17:30:07 +0000 [thread overview]
Message-ID: <163526940738.14989.1405994833076830797.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211026152939.3125950-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 26 Oct 2021 08:29:39 -0700 you wrote:
> revert commit 46ae40b94d88 ("net/mlx5: Let user configure io_eq_size param")
> revert commit a6cb08daa3b4 ("net/mlx5: Let user configure event_eq_size param")
> revert commit 554604061979 ("net/mlx5: Let user configure max_macs param")
>
> The EQE parameters are applicable to more drivers, they should
> be configured via standard API, probably ethtool. Example of
> another driver needing something similar:
>
> [...]
Here is the summary with links:
- [net-next] net/mlx5: remove the recent devlink params
https://git.kernel.org/netdev/net-next/c/6b3671746a8a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-10-26 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 15:29 [PATCH net-next] net/mlx5: remove the recent devlink params Jakub Kicinski
2021-10-26 15:53 ` Parav Pandit
2021-10-26 16:47 ` Jakub Kicinski
2021-10-26 19:11 ` Saeed Mahameed
2021-10-26 16:45 ` Leon Romanovsky
2021-10-26 16:47 ` Jakub Kicinski
2021-10-26 17:30 ` patchwork-bot+netdevbpf [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=163526940738.14989.1405994833076830797.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--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.