From: "Jiang, YuX" <yux.jiang@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev (dev@dpdk.org)" <dev@dpdk.org>,
"Devlin, Michelle" <michelle.devlin@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.08-rc3
Date: Thu, 5 Aug 2021 10:35:46 +0000 [thread overview]
Message-ID: <SJ0PR11MB5150D4196A5A7B90F53D5CAEFEF29@SJ0PR11MB5150.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3109301.L01GMEPFAE@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Wednesday, August 4, 2021 8:48 PM
> To: Jiang, YuX <yux.jiang@intel.com>
> Cc: dev (dev@dpdk.org) <dev@dpdk.org>; Devlin, Michelle
> <michelle.devlin@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>; Zhang,
> Qi Z <qi.z.zhang@intel.com>
> Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.08-rc3
>
> 04/08/2021 13:38, Jiang, YuX:
> > Hi Thomas and all,
> > Update the test status for Intel part. Till now dpdk21.08-rc3 test is finished.
> No critical issue is found.
> > One bug about https://bugs.dpdk.org/show_bug.cgi?id=768 is found,
> Nvidia's Dev. is working on it.
>
> No, there is no work on NVIDIA side, because it seems to reveal an issue on
> Intel driver side, as I said in the mail thread.
>
Ok. Thanks Thomas, we will check it on Intel side.
prev parent reply other threads:[~2021-08-05 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 21:19 Thomas Monjalon
2021-08-03 5:34 ` Kalesh Anakkur Purayil
2021-08-03 17:36 ` Thinh Tran
2021-08-04 11:38 ` Jiang, YuX
2021-08-04 12:48 ` Thomas Monjalon
2021-08-05 10:35 ` Jiang, YuX [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=SJ0PR11MB5150D4196A5A7B90F53D5CAEFEF29@SJ0PR11MB5150.namprd11.prod.outlook.com \
--to=yux.jiang@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).