DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Yu, PingX" <pingx.yu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 20.11-rc4
Date: Thu, 19 Nov 2020 09:46:54 +0000	[thread overview]
Message-ID: <BY5PR11MB39733E8F7346197B7A3AE9B085E00@BY5PR11MB3973.namprd11.prod.outlook.com> (raw)
In-Reply-To: <4017285.oMJDOflQix@thomas>

All,
20.11-rc4 test from Intel part is almost done. No new issue except below one.
Issue: start testpmd failed with max-pkt-len param.
It effected all of jumboframe feature.  Ferruh has summitted a new patch to revert the bad commit id on rc5.  

Regards,
Yu Ping

> -----Original Message-----
> From: announce <announce-bounces@dpdk.org> On Behalf Of Thomas
> Monjalon
> Sent: Monday, November 16, 2020 7:32 AM
> To: announce@dpdk.org
> Subject: [dpdk-announce] release candidate 20.11-rc4
> 
> A new DPDK release candidate is ready for testing:
> 	https://git.dpdk.org/dpdk/tag/?id=v20.11-rc4
> 
> There are 148 new patches in this snapshot.
> 
> Release notes:
> 	http://doc.dpdk.org/guides/rel_notes/release_20_11.html
> 
> The -rc5 will include only critical bug fixes, doc and tooling.
> 
> Please test, report and fix issues on bugs.dpdk.org.
> You may share some release validation results by replying to this message (at
> dev@dpdk.org).
> 
> Please share your roadmap for 21.02 to get high priority.
> Planning is especially important to avoid flooding maintainers.
> 
> Thank you everyone
> 


      reply	other threads:[~2020-11-19  9:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-15 23:32 Thomas Monjalon
2020-11-19  9:46 ` Yu, PingX [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=BY5PR11MB39733E8F7346197B7A3AE9B085E00@BY5PR11MB3973.namprd11.prod.outlook.com \
    --to=pingx.yu@intel.com \
    --cc=dev@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;
as well as URLs for NNTP newsgroup(s).