DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "Jiang, YuX" <yux.jiang@intel.com>,
	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: Mon, 21 Nov 2022 14:13:17 +0000	[thread overview]
Message-ID: <e6df9a81-9559-cb23-6fbb-278a544eff85@amd.com> (raw)
In-Reply-To: <BYAPR11MB27114256FBD2E3B285DCEC12FE0A9@BYAPR11MB2711.namprd11.prod.outlook.com>

On 11/21/2022 1:50 PM, Jiang, YuX wrote:
> Update the test status for Intel part. Till now dpdk22.11-rc3 validation test is almost finished.
> 3 bugs are found, Bug1 & Bug2 are critical issues, hope they can be fixed in 22.11.
>   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 v4 dpdk patch(https://patches.dpdk.org/project/dpdk/patch/20221118141334.3825072-1-hpothula@marvell.com/), test passed.

Hi Yu,

Can you please verify v5 too?
https://patches.dpdk.org/project/dpdk/patch/20221121124546.3920722-1-hpothula@marvell.com/

There will be a v6 too, but I expect the logic will be same but it will
have some code reordering and documentation update.

Thanks,
ferruh

  reply	other threads:[~2022-11-21 14:13 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 [this message]
2022-11-22 10:17     ` Jiang, YuX
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=e6df9a81-9559-cb23-6fbb-278a544eff85@amd.com \
    --to=ferruh.yigit@amd.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 \
    --cc=yux.jiang@intel.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).