From: Stephen Hemminger <stephen@networkplumber.org>
To: mark-blasko <blasko@google.com>
Cc: dev@dpdk.org, Joshua Washington <joshwash@google.com>,
"Jasper Tran O'Leary" <jtranoleary@google.com>
Subject: Re: [PATCH 6/6] net/gve: reconstruct HW timestamps from DQO
Date: Tue, 12 May 2026 10:26:03 +0200 [thread overview]
Message-ID: <20260512102603.6637cf79@stephen-xps.local> (raw)
In-Reply-To: <20260512005057.944672-7-blasko@google.com>
On Tue, 12 May 2026 00:50:55 +0000
mark-blasko <blasko@google.com> wrote:
> diff --git a/doc/guides/rel_notes/release_26_07.rst b/doc/guides/rel_notes/release_26_07.rst
> index 1b012c4776..db886f19cf 100644
> --- a/doc/guides/rel_notes/release_26_07.rst
> +++ b/doc/guides/rel_notes/release_26_07.rst
> @@ -62,6 +62,9 @@ New Features
> * ``-A`` or ``--no-auto-probing`` disable the initial bus probing: no device is probed during
> ``rte_eal_init`` and the application is responsible for probing each device,
> * ``--auto-probing`` enables the initial bus probing, which is the current default behavior.
> +* **Updated Google GVE net driver.**
> +
> + * Added hardware timestamping support on DQO queues.
>
> * **Updated PCAP ethernet driver.**
Need blank line between release note entries.
Run doc build to see errors like this
next prev parent reply other threads:[~2026-05-12 8:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 0:50 [PATCH 0/6] net/gve: add hardware timestamping support mark-blasko
2026-05-12 0:50 ` [PATCH 1/6] net/gve: add thread safety to admin queue mark-blasko
2026-05-12 0:50 ` [PATCH 2/6] net/gve: add device option support for HW timestamps mark-blasko
2026-05-12 0:50 ` [PATCH 3/6] net/gve: add AdminQ command for NIC timestamps mark-blasko
2026-05-12 0:50 ` [PATCH 4/6] net/gve: add periodic NIC clock synchronization mark-blasko
2026-05-12 0:50 ` [PATCH 5/6] net/gve: support read clock ethdev op mark-blasko
2026-05-12 0:50 ` [PATCH 6/6] net/gve: reconstruct HW timestamps from DQO mark-blasko
2026-05-12 8:26 ` Stephen Hemminger [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-12 0:53 [PATCH 0/6] net/gve: add hardware timestamping support Mark Blasko
2026-05-12 0:53 ` [PATCH 6/6] net/gve: reconstruct HW timestamps from DQO Mark Blasko
2026-05-11 22:43 [PATCH 0/6] net/gve: add hardware timestamping support mark-blasko
2026-05-11 22:43 ` [PATCH 6/6] net/gve: reconstruct HW timestamps from DQO mark-blasko
2026-05-11 22:22 [PATCH 0/6] net/gve: add hardware timestamping support mark-blasko
2026-05-11 22:23 ` [PATCH 6/6] net/gve: reconstruct HW timestamps from DQO mark-blasko
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=20260512102603.6637cf79@stephen-xps.local \
--to=stephen@networkplumber.org \
--cc=blasko@google.com \
--cc=dev@dpdk.org \
--cc=joshwash@google.com \
--cc=jtranoleary@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 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.