From: patchwork-bot+netdevbpf@kernel.org
To: Song@ci.codeaurora.org, Yoong Siang <yoong.siang.song@intel.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
john.fastabend@gmail.com, sdf@google.com, alexanderduyck@fb.com,
brouer@redhat.com, boon.leong.ong@intel.com,
jacob.e.keller@intel.com, netdev@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
xdp-hints@xdp-project.net
Subject: [xdp-hints] Re: [PATCH net-next v6 0/3] XDP Rx HWTS metadata for stmmac driver
Date: Tue, 18 Apr 2023 02:10:19 +0000 [thread overview]
Message-ID: <168178381968.5081.7896199883043114155.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230415064503.3225835-1-yoong.siang.song@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 15 Apr 2023 14:45:00 +0800 you wrote:
> Implemented XDP receive hardware timestamp metadata for stmmac driver.
>
> This patchset is tested with tools/testing/selftests/bpf/xdp_hw_metadata.
> Below are the test steps and results.
>
> Command on DUT:
> sudo ./xdp_hw_metadata <interface name>
>
> [...]
Here is the summary with links:
- [net-next,v6,1/3] net: stmmac: introduce wrapper for struct xdp_buff
https://git.kernel.org/netdev/net-next/c/5b24324a907c
- [net-next,v6,2/3] net: stmmac: add Rx HWTS metadata to XDP receive pkt
https://git.kernel.org/netdev/net-next/c/e3f9c3e34840
- [net-next,v6,3/3] net: stmmac: add Rx HWTS metadata to XDP ZC receive pkt
https://git.kernel.org/netdev/net-next/c/9570df353309
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:[~2023-04-18 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 6:45 [xdp-hints] " Song Yoong Siang
2023-04-15 6:45 ` [xdp-hints] [PATCH net-next v6 1/3] net: stmmac: introduce wrapper for struct xdp_buff Song Yoong Siang
2023-04-15 6:45 ` [xdp-hints] [PATCH net-next v6 2/3] net: stmmac: add Rx HWTS metadata to XDP receive pkt Song Yoong Siang
2023-04-15 9:33 ` [xdp-hints] " Jesper Dangaard Brouer
2023-04-15 6:45 ` [xdp-hints] [PATCH net-next v6 3/3] net: stmmac: add Rx HWTS metadata to XDP ZC " Song Yoong Siang
2023-04-15 9:34 ` [xdp-hints] " Jesper Dangaard Brouer
2023-04-18 2:10 ` 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
List information: https://lists.xdp-project.net/postorius/lists/xdp-hints.xdp-project.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=168178381968.5081.7896199883043114155.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Song@ci.codeaurora.org \
--cc=alexanderduyck@fb.com \
--cc=alexandre.torgue@foss.st.com \
--cc=ast@kernel.org \
--cc=boon.leong.ong@intel.com \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=joabreu@synopsys.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=sdf@google.com \
--cc=xdp-hints@xdp-project.net \
--cc=yoong.siang.song@intel.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