From: patchwork-bot+netdevbpf@kernel.org
To: Louis Peens <louis.peens@corigine.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
simon.horman@corigine.com, netdev@vger.kernel.org,
oss-drivers@corigine.com
Subject: Re: [PATCH net-next] nfp: improve link modes reading process
Date: Wed, 10 May 2023 02:50:26 +0000 [thread overview]
Message-ID: <168368702618.23144.3048175947408525868.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230509075817.10566-1-louis.peens@corigine.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 9 May 2023 09:58:17 +0200 you wrote:
> From: Yinjun Zhang <yinjun.zhang@corigine.com>
>
> Avoid reading link modes from management firmware every time when
> `ethtool_get_link_ksettings` is called, only communicate with
> management firmware when necessary like we do for eth_table info.
>
> This change can ease the situation that when large number of vlan
> sub-interfaces are created and their information is requested by
> some monitoring process like PCP [1] through ethool ioctl frequently.
>
> [...]
Here is the summary with links:
- [net-next] nfp: improve link modes reading process
https://git.kernel.org/netdev/net-next/c/a731a43e8669
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:[~2023-05-10 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 7:58 [PATCH net-next] nfp: improve link modes reading process Louis Peens
2023-05-09 8:13 ` Leon Romanovsky
2023-05-10 2:50 ` 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=168368702618.23144.3048175947408525868.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.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.