From: patchwork-bot+netdevbpf@kernel.org
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
edwin.peer@broadcom.com, gospo@broadcom.com,
florian.fainelli@broadcom.com
Subject: Re: [PATCH net-next v2] bnxt_en: Fix 64-bit doorbell operation on 32-bit kernels
Date: Wed, 01 Sep 2021 10:50:06 +0000 [thread overview]
Message-ID: <163049340641.3899.2784210096565039659.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1630458923-14161-1-git-send-email-michael.chan@broadcom.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Tue, 31 Aug 2021 21:15:23 -0400 you wrote:
> The driver requires 64-bit doorbell writes to be atomic on 32-bit
> architectures. So we redefined writeq as a new macro with spinlock
> protection on 32-bit architectures. This created a new warning when
> we added a new file in a recent patchset. writeq is defined on many
> 32-bit architectures to do the memory write non-atomically and it
> generated a new macro redefined warning. This warning was fixed
> incorrectly in the recent patch.
>
> [...]
Here is the summary with links:
- [net-next,v2] bnxt_en: Fix 64-bit doorbell operation on 32-bit kernels
https://git.kernel.org/netdev/net/c/c6132f6f2e68
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-09-01 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 1:15 [PATCH net-next v2] bnxt_en: Fix 64-bit doorbell operation on 32-bit kernels Michael Chan
2021-09-01 1:46 ` Florian Fainelli
2021-09-01 10: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=163049340641.3899.2784210096565039659.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edwin.peer@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=gospo@broadcom.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).