From: patchwork-bot+netdevbpf@kernel.org
To: Emanuele Rocca <emanuele.rocca@arm.com>
Cc: sgoutham@marvell.com, gakula@marvell.com, rkannoth@marvell.com,
sbhatta@marvell.com, bbhushan2@marvell.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, schalla@marvell.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Tamar.Christina@arm.com,
Jeremy.Linton@arm.com
Subject: Re: [PATCH net] octeontx2: use arch_extension to enable LSE
Date: Thu, 08 Oct 2026 23:50:04 +0000 [thread overview]
Message-ID: <179150340428.483817.886115147971378041.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261005162137.71397-1-emanuele.rocca@arm.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 5 Oct 2026 18:21:37 +0200 you wrote:
> Instead of using ".cpu generic+lse", use ".arch_extension lse" to
> enable LSE.
>
> The ".cpu generic+lse" directive replaces the assembler's current feature
> set with generic+lse, dropping other previously enabled features. In
> contrast, ".arch_extension lse" enables LSE while preserving the current
> feature set.
>
> [...]
Here is the summary with links:
- [net] octeontx2: use arch_extension to enable LSE
https://git.kernel.org/netdev/net-next/c/9142c2f8f84b
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-10-08 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 16:21 [PATCH net] octeontx2: use arch_extension to enable LSE Emanuele Rocca
2026-10-05 17:01 ` [EXTERNAL] " Geethasowjanya Akula
2026-10-06 8:42 ` Geethasowjanya Akula
2026-10-08 23: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=179150340428.483817.886115147971378041.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Jeremy.Linton@arm.com \
--cc=Tamar.Christina@arm.com \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=emanuele.rocca@arm.com \
--cc=gakula@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rkannoth@marvell.com \
--cc=sbhatta@marvell.com \
--cc=schalla@marvell.com \
--cc=sgoutham@marvell.com \
/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