From: "Jiang, YuX" <yux.jiang@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"dev (dev@dpdk.org)" <dev@dpdk.org>
Cc: "Devlin, Michelle" <michelle.devlin@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: RE: release candidate 22.11-rc3
Date: Tue, 22 Nov 2022 10:17:54 +0000 [thread overview]
Message-ID: <BYAPR11MB271162A01B63BEDA42061998FE0D9@BYAPR11MB2711.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BYAPR11MB27114256FBD2E3B285DCEC12FE0A9@BYAPR11MB2711.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Jiang, YuX
> Sent: Monday, November 21, 2022 9:51 PM
> To: 'Thomas Monjalon' <thomas@monjalon.net>; dev (dev@dpdk.org)
> <dev@dpdk.org>
> Cc: Devlin, Michelle <michelle.devlin@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Richardson, Bruce
> <bruce.richardson@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
> Subject: RE: release candidate 22.11-rc3
>
> > -----Original Message-----
> > From: Jiang, YuX
> > Sent: Thursday, November 17, 2022 4:49 PM
> > To: Thomas Monjalon <thomas@monjalon.net>; dev (dev@dpdk.org)
> > <dev@dpdk.org>
> > Cc: Devlin, Michelle <michelle.devlin@intel.com>; Mcnamara, John
> > <john.mcnamara@intel.com>; Richardson, Bruce
> > <bruce.richardson@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
> > Subject: RE: release candidate 22.11-rc3
> >
> > > -----Original Message-----
> > > From: Thomas Monjalon <thomas@monjalon.net>
> > > Sent: Wednesday, November 16, 2022 1:33 AM
> > > To: announce@dpdk.org
> > > Subject: release candidate 22.11-rc3
> > >
> > > A new DPDK release candidate is ready for testing:
> > > https://git.dpdk.org/dpdk/tag/?id=v22.11-rc3
> > >
> > > There are 161 new patches in this snapshot.
> > >
> > > Release notes:
> > > https://doc.dpdk.org/guides/rel_notes/release_22_11.html
> > >
> > > Please test and report issues on bugs.dpdk.org.
> > > You may share some release validation results by replying to this
> > > message at dev@dpdk.org and by adding tested hardware in the release
> > notes.
> > >
> > > DPDK 22.11-rc4 should be the last chance for bug fixes and doc
> > > updates, and it is planned for the end of this week.
> > >
> > > Thank you everyone
> > >
> >
>
Bug1： https://bugs.dpdk.org/show_bug.cgi?id=1128 [dpdk22.11-rc3]failed to start testpmd with the mbuf-size parameter
- Bad commit 4f04edcda769770881832f8036fd209e7bb6ab9a
- Verify v7 dpdk patch(https://patches.dpdk.org/project/dpdk/patch/20221121180756.3924770-1-hpothula@marvell.com/), test passed.
Bug2: idpf: core dumped when launch l3fwd with 1c1q & Bug3: [DPDK22.11] idpf: failed to start port all.
- All are fixed on latest main dpdk.
Best regards,
Yu Jiang
next prev parent reply other threads:[~2022-11-22 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 17:32 Thomas Monjalon
2022-11-17 8:20 ` David Marchand
2022-11-17 8:48 ` Jiang, YuX
2022-11-21 13:50 ` Jiang, YuX
2022-11-21 14:13 ` Ferruh Yigit
2022-11-22 10:17 ` Jiang, YuX [this message]
2022-11-20 15:47 ` Wael Abualrub
2022-11-21 20:22 ` Thinh Tran
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=BYAPR11MB271162A01B63BEDA42061998FE0D9@BYAPR11MB2711.namprd11.prod.outlook.com \
--to=yux.jiang@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=michelle.devlin@intel.com \
--cc=qi.z.zhang@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).