From: patchwork-bot+netdevbpf@kernel.org
To: Asmaa Mnebhi <asmaa@nvidia.com>
Cc: davem@davemloft.net, f.fainelli@gmail.com, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, tbogendoerfer@suse.de,
horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, davthompson@nvidia.com,
florian.fainelli@broadcom.com
Subject: Re: [PATCH net v4] mlxbf_gige: Enable the GigE port in mlxbf_gige_open
Date: Sun, 07 Jan 2024 15:30:24 +0000 [thread overview]
Message-ID: <170464142421.16555.13169210527122295576.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240105160014.23353-1-asmaa@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 5 Jan 2024 11:00:14 -0500 you wrote:
> At the moment, the GigE port is enabled in the mlxbf_gige_probe
> function. If the mlxbf_gige_open is not executed, this could cause
> pause frames to increase in the case where there is high backgroud
> traffic. This results in clogging the port.
> So move enabling the OOB port to mlxbf_gige_open.
>
> Fixes: f92e1869d74e ("Add Mellanox BlueField Gigabit Ethernet driver")
> Reviewed-by: David Thompson <davthompson@nvidia.com>
> Signed-off-by: Asmaa Mnebhi <asmaa@nvidia.com>
> Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
>
> [...]
Here is the summary with links:
- [net,v4] mlxbf_gige: Enable the GigE port in mlxbf_gige_open
https://git.kernel.org/netdev/net/c/a460f4a68451
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:[~2024-01-07 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-05 16:00 [PATCH net v4] mlxbf_gige: Enable the GigE port in mlxbf_gige_open Asmaa Mnebhi
2024-01-07 15: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=170464142421.16555.13169210527122295576.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=asmaa@nvidia.com \
--cc=davem@davemloft.net \
--cc=davthompson@nvidia.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tbogendoerfer@suse.de \
/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