From: Kevin Traynor <ktraynor@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Shani Peretz <shperetz@nvidia.com>
Cc: stable@dpdk.org, dev@dpdk.org, Luca Boccassi <bluca@debian.org>,
Robin Jarry <rjarry@redhat.com>,
David Marchand <david.marchand@redhat.com>
Subject: Re: 23.11.7 patches review and test
Date: Thu, 30 Apr 2026 11:02:57 +0100 [thread overview]
Message-ID: <f27bd211-66c0-4a87-9d11-de6d83cae4c9@redhat.com> (raw)
In-Reply-To: <2787587.q0ZmV6gNhb@thomas>
On 4/30/26 10:58 AM, Thomas Monjalon wrote:
> 30/04/2026 11:32, Kevin Traynor:
>> On 4/21/26 7:46 AM, Shani Peretz wrote:
>>> The planned date for the final release is 30 April 2026.
>>
>> As discussed on thread [0] there was a quite serious regression caused
>> by "net: fix packet type for stacked VLAN"
>>
>> As discussion on the fix is ongoing, I would suggest to just revert this
>> patch for your release.
>
> I agree the revert is the best option here.
>
>> It doesn't require a new RC and re-validation as it's an isolated issue
>> (and there wasn't test cases to catch before Robin's new patch anyway)
>
> I suppose 24.11.5 and 25.11.1 are also impacted?
>
>
Yes, I was hoping we would have a fix in a few days and we could add and
re-release. Given that there's now discussion on the patch and what
functionality is needed, it's probably best to just revert and release a
new 24.11/25.11.
next prev parent reply other threads:[~2026-04-30 10:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 6:46 23.11.7 patches review and test Shani Peretz
2026-04-29 17:57 ` Ali Alnubani
2026-05-05 16:05 ` Shani Peretz
2026-04-30 1:29 ` Xu, HailinX
2026-05-05 16:05 ` Shani Peretz
2026-04-30 9:32 ` Kevin Traynor
2026-04-30 9:58 ` Thomas Monjalon
2026-04-30 10:02 ` Kevin Traynor [this message]
2026-05-15 10:31 ` Kevin Traynor
2026-05-15 12:36 ` Luca Boccassi
2026-05-15 16:03 ` Kevin Traynor
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=f27bd211-66c0-4a87-9d11-de6d83cae4c9@redhat.com \
--to=ktraynor@redhat.com \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=rjarry@redhat.com \
--cc=shperetz@nvidia.com \
--cc=stable@dpdk.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