public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Joshua Washington <joshwash@google.com>
Cc: netdev@vger.kernel.org, hramamurthy@google.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, richardcochran@gmail.com,
	ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
	john.fastabend@gmail.com, sdf@fomichev.me, willemb@google.com,
	pkaligineedi@google.com, thostet@google.com, yyd@google.com,
	linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] gve: Implement XDP HW RX Timestamping support for DQ
Date: Tue, 18 Nov 2025 15:00:12 +0000	[thread overview]
Message-ID: <176347801225.4178761.8286232845240261074.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251114211146.292068-1-joshwash@google.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 14 Nov 2025 13:11:42 -0800 you wrote:
> From: Tim Hostetler <thostet@google.com>
> 
> This patch series adds support for bpf_xdp_metadata_rx_timestamp from an
> XDP program loaded into the driver on its own or bound to an XSK. This
> is only supported for DQ.
> 
> Tim Hostetler (4):
>   gve: Move ptp_schedule_worker to gve_init_clock
>   gve: Wrap struct xdp_buff
>   gve: Prepare bpf_xdp_metadata_rx_timestamp support
>   gve: Add Rx HWTS metadata to AF_XDP ZC mode

Here is the summary with links:
  - [net-next,1/4] gve: Move ptp_schedule_worker to gve_init_clock
    https://git.kernel.org/netdev/net-next/c/46e7860ef941
  - [net-next,2/4] gve: Wrap struct xdp_buff
    https://git.kernel.org/netdev/net-next/c/f356a66b87bb
  - [net-next,3/4] gve: Prepare bpf_xdp_metadata_rx_timestamp support
    https://git.kernel.org/netdev/net-next/c/66adaf102128
  - [net-next,4/4] gve: Add Rx HWTS metadata to AF_XDP ZC mode
    https://git.kernel.org/netdev/net-next/c/1b42e07af1ee

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-11-18 15:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 21:11 [PATCH net-next 0/4] gve: Implement XDP HW RX Timestamping support for DQ joshwash
2025-11-14 21:11 ` [PATCH net-next 1/4] gve: Move ptp_schedule_worker to gve_init_clock joshwash
2025-11-14 21:11 ` [PATCH net-next 2/4] gve: Wrap struct xdp_buff joshwash
2025-11-14 21:11 ` [PATCH net-next 3/4] gve: Prepare bpf_xdp_metadata_rx_timestamp support joshwash
2025-11-14 21:11 ` [PATCH net-next 4/4] gve: Add Rx HWTS metadata to AF_XDP ZC mode joshwash
2025-11-18 15: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=176347801225.4178761.8286232845240261074.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=hramamurthy@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=joshwash@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pkaligineedi@google.com \
    --cc=richardcochran@gmail.com \
    --cc=sdf@fomichev.me \
    --cc=thostet@google.com \
    --cc=willemb@google.com \
    --cc=yyd@google.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