From: patchwork-bot+netdevbpf@kernel.org
To: Raju Rangoju <Raju.Rangoju@amd.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, kuba@kernel.org,
edumazet@google.com, davem@davemloft.net, andrew+netdev@lunn.ch,
linux-kernel@vger.kernel.org, Shyam-sundar.S-k@amd.com
Subject: Re: [PATCH net-next v3 0/4] amd-xgbe: add ARP offload and RSS self-tests
Date: Fri, 06 Feb 2026 03:20:05 +0000 [thread overview]
Message-ID: <177034800558.667103.17338829057267608247.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260204145829.801839-1-Raju.Rangoju@amd.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 4 Feb 2026 20:28:29 +0530 you wrote:
> This series adds ARP offload support and ethtool self-tests for the
> AMD XGBE 10 Gigabit Ethernet driver.
>
> Patch 1 is a build fix for randconfig coverage.
>
> Patch 2 adds hardware ARP offload functionality that allows the MAC
> to automatically respond to ARP requests without CPU intervention,
> reducing system latency and power consumption during suspend/resume
> and normal operation.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/4] amd-xgbe: do not select NET_SELFTESTS when INET is disabled
https://git.kernel.org/netdev/net/c/ee9241524b46
- [net-next,v3,2/4] amd-xgbe: add hardware ARP offload support
(no matching commit)
- [net-next,v3,3/4] amd-xgbe: add ARP offload ethtool self-test
(no matching commit)
- [net-next,v3,4/4] amd-xgbe: add RSS ethtool self-test
(no matching commit)
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-02-06 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 14:58 [PATCH net-next v3 0/4] amd-xgbe: add ARP offload and RSS self-tests Raju Rangoju
2026-02-06 3:09 ` Jakub Kicinski
2026-02-06 3:20 ` 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=177034800558.667103.17338829057267608247.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Raju.Rangoju@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.