From: Luca Boccassi <luca.boccassi@gmail.com>
To: "Minggang(Gavin) Li" <gavinl@nvidia.com>
Cc: Maayan Kashani <mkashani@nvidia.com>,
Ali Alnubani <alialnu@nvidia.com>,
Shani Peretz <shperetz@nvidia.com>,
Kevin Traynor <ktraynor@redhat.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>,
John McNamara <john.mcnamara@intel.com>,
Raslan Darawsheh <rasland@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Salaheddin Badawi <sbadawi@nvidia.com>,
Wael Abualrub <waela@nvidia.com>
Subject: Re: 22.11.11 patches review and test
Date: Wed, 24 Dec 2025 13:06:46 +0000 [thread overview]
Message-ID: <CAMw=ZnRHg=0sKmZa72amrSgALsn7LoTS0U_o1UXKwk1s0c9Mig@mail.gmail.com> (raw)
In-Reply-To: <IA1PR12MB6628D5EE5A1CBDF44D9F1408B3B2A@IA1PR12MB6628.namprd12.prod.outlook.com>
On Wed, 24 Dec 2025 at 10:12, Minggang(Gavin) Li <gavinl@nvidia.com> wrote:
>
> Sorry @Luca Boccassi, @Shani Peretz and @Kevin Traynor,
> I double checked the first commit of the three and found that I did tag it with CC stable but missed the following commits to fix a bug introduce by it. This is the root cause of the mess made by me. The first commit introduced behavior change that should not be backported to stable branches.
> Please revert the commits mentioned.
Ok no problem, thanks for checking, I'll revert and proceed with the release
prev parent reply other threads:[~2025-12-24 13:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 0:56 luca.boccassi
2025-12-08 8:03 ` Yanghang Liu
2025-12-08 10:28 ` Luca Boccassi
2025-12-12 6:51 ` Xu, HailinX
2025-12-12 6:53 ` Xu, HailinX
2025-12-12 12:25 ` Luca Boccassi
2025-12-18 18:23 ` Ali Alnubani
2025-12-18 18:27 ` Luca Boccassi
2025-12-18 18:58 ` Ali Alnubani
2025-12-18 19:06 ` Luca Boccassi
2025-12-22 11:26 ` Luca Boccassi
2025-12-23 14:09 ` Maayan Kashani
2025-12-24 3:09 ` Minggang(Gavin) Li
2025-12-24 7:33 ` Maayan Kashani
2025-12-24 10:12 ` Minggang(Gavin) Li
2025-12-24 13:06 ` Luca Boccassi [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='CAMw=ZnRHg=0sKmZa72amrSgALsn7LoTS0U_o1UXKwk1s0c9Mig@mail.gmail.com' \
--to=luca.boccassi@gmail.com \
--cc=alialnu@nvidia.com \
--cc=dev@dpdk.org \
--cc=gavinl@nvidia.com \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=mkashani@nvidia.com \
--cc=rasland@nvidia.com \
--cc=sbadawi@nvidia.com \
--cc=shperetz@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=waela@nvidia.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;
as well as URLs for NNTP newsgroup(s).