From: patchwork-bot+netdevbpf@kernel.org
To: Vadim Fedorenko <vadfed@meta.com>
Cc: vadim.fedorenko@linux.dev, michael.chan@broadcom.com,
pavan.chebbi@broadcom.com, kuba@kernel.org,
andrew+netdev@lunn.ch, pabeni@redhat.com, davem@davemloft.net,
netdev@vger.kernel.org, richardcochran@gmail.com
Subject: Re: [PATCH net-next v2] bnxt_en: add unlocked version of bnxt_refclk_read
Date: Tue, 12 Nov 2024 01:40:32 +0000 [thread overview]
Message-ID: <173137563274.43860.8599488490188476265.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241107214917.2980976-1-vadfed@meta.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 7 Nov 2024 13:49:17 -0800 you wrote:
> Serialization of PHC read with FW reset mechanism uses ptp_lock which
> also protects timecounter updates. This means we cannot grab it when
> called from bnxt_cc_read(). Let's move locking into different function.
>
> Fixes: 6c0828d00f07 ("bnxt_en: replace PTP spinlock with seqlock")
> Signed-off-by: Vadim Fedorenko <vadfed@meta.com>
>
> [...]
Here is the summary with links:
- [net-next,v2] bnxt_en: add unlocked version of bnxt_refclk_read
https://git.kernel.org/netdev/net-next/c/f0fe51a04386
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-11-12 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 21:49 [PATCH net-next v2] bnxt_en: add unlocked version of bnxt_refclk_read Vadim Fedorenko
2024-11-08 4:48 ` Pavan Chebbi
2024-11-12 1:40 ` 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=173137563274.43860.8599488490188476265.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=richardcochran@gmail.com \
--cc=vadfed@meta.com \
--cc=vadim.fedorenko@linux.dev \
/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.