From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Thomas Monjalon" <thomas@monjalon.net>
Cc: <dev@dpdk.org>, <stable@dpdk.org>,
"Maxime Leroy" <maxime@leroys.fr>,
"Stephen Hemminger" <stephen@networkplumber.org>
Subject: RE: [PATCH] net: revert add IPv6 traffic class and flow label fields
Date: Mon, 28 Sep 2026 16:20:22 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F65A80@smartserver.smartshare.dk> (raw)
In-Reply-To: <endP4k7ET0iyFdUNMs3orQ@monjalon.net>
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: Monday, 28 September 2026 16.15
>
> Hello, are we waiting for a v2?
OK.
Will send a v2 with improved commit message and release notes, as suggested by Stephen's AI.
-Morten
next prev parent reply other threads:[~2026-09-28 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 16:36 [PATCH] net: revert add IPv6 traffic class and flow label fields Morten Brørup
2026-09-22 18:14 ` Stephen Hemminger
2026-09-28 14:15 ` Thomas Monjalon
2026-09-28 14:20 ` Morten Brørup [this message]
2026-09-29 7:36 ` [PATCH v2] " Morten Brørup
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=98CBD80474FA8B44BF855DF32C47DC35F65A80@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=maxime@leroys.fr \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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