public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: David Thompson <davthompson@nvidia•com>
Cc: davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
	pabeni@redhat•com, netdev@vger•kernel.org, cai.huoqing@linux•dev,
	brgl@bgdev•pl, limings@nvidia•com, asmaa@nvidia•com
Subject: Re: [PATCH net v1] mlxbf_gige: clear MDIO gateway lock after read
Date: Mon, 19 Sep 2022 21:30:14 +0000	[thread overview]
Message-ID: <166362301458.9084.5292056267200738171.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220902164247.19862-1-davthompson@nvidia.com>

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel•org>:

On Fri, 2 Sep 2022 12:42:47 -0400 you wrote:
> The MDIO gateway (GW) lock in BlueField-2 GIGE logic is
> set after read.  This patch adds logic to make sure the
> lock is always cleared at the end of each MDIO transaction.
> 
> Fixes: f92e1869d74e ("Add Mellanox BlueField Gigabit Ethernet driver")
> Reviewed-by: Asmaa Mnebhi <asmaa@nvidia•com>
> Signed-off-by: David Thompson <davthompson@nvidia•com>
> 
> [...]

Here is the summary with links:
  - [net,v1] mlxbf_gige: clear MDIO gateway lock after read
    https://git.kernel.org/netdev/net/c/182447b12144

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2022-09-19 21:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02 16:42 [PATCH net v1] mlxbf_gige: clear MDIO gateway lock after read David Thompson
2022-09-19 21: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=166362301458.9084.5292056267200738171.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=asmaa@nvidia$(echo .)com \
    --cc=brgl@bgdev$(echo .)pl \
    --cc=cai.huoqing@linux$(echo .)dev \
    --cc=davem@davemloft$(echo .)net \
    --cc=davthompson@nvidia$(echo .)com \
    --cc=edumazet@google$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=limings@nvidia$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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