From: patchwork-bot+netdevbpf@kernel.org
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew+netdev@lunn.ch,
pavan.chebbi@broadcom.com, andrew.gospodarek@broadcom.com,
sfr@canb.auug.org.au, lkp@intel.com
Subject: Re: [PATCH net-next] bnxt_en: Fix build break on non-x86 platforms
Date: Fri, 16 Jan 2026 04:00:40 +0000 [thread overview]
Message-ID: <176853604027.76642.5758429555721967161.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260113183422.508851-1-michael.chan@broadcom.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 13 Jan 2026 10:34:22 -0800 you wrote:
> From: Pavan Chebbi <pavan.chebbi@broadcom.com>
>
> Commit c470195b989fe added .getcrosststamp() interface where
> the code uses boot_cpu_has() function which is available only
> in x86 platforms. This fails the build on any other platform.
>
> Since the interface is going to be supported only on x86 anyway,
> we can simply compile out the entire support on non-x86 platforms.
>
> [...]
Here is the summary with links:
- [net-next] bnxt_en: Fix build break on non-x86 platforms
https://git.kernel.org/netdev/net-next/c/dc634118aaa0
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:[~2026-01-16 4:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 18:34 [PATCH net-next] bnxt_en: Fix build break on non-x86 platforms Michael Chan
2026-01-14 0:00 ` Vadim Fedorenko
2026-01-16 4:00 ` 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=176853604027.76642.5758429555721967161.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lkp@intel.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=sfr@canb.auug.org.au \
/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