patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
	"benjamin.walker@intel.com" <benjamin.walker@intel.com>,
	David Christensen <drc@linux.vnet.ibm.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Ian Stokes <ian.stokes@intel.com>,
	Jerin Jacob <jerinj@marvell.com>,
	John McNamara <john.mcnamara@intel.com>,
	Ju-Hyoung Lee <juhlee@microsoft.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
	"qian.q.xu@intel.com" <qian.q.xu@intel.com>,
	Raslan Darawsheh <rasland@nvidia.com>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	"yuan.peng@intel.com" <yuan.peng@intel.com>,
	"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: RE: 19.11.12 patches review and test
Date: Mon, 4 Apr 2022 07:02:45 +0000	[thread overview]
Message-ID: <DM4PR12MB51672B5D787385F6529780ECDAE59@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAATJJ0J=G0TnUreyF+cyizk=GCpumRLEXSwB+rN+z4jQa07LbQ@mail.gmail.com>

Hi Christian,

[..]
> Of the parties usually verifying the 19.11.x release I'm still missing to hear anything from Redhat and Nvidia.
> I'd be happy if you could let me know if your results will be:
>   a) in time for Wednesday
>   b) delayed a bit
>   c) or if I should not wait for them
[..]

Just sent out our results with Nvidia hardware, and we're ok with the release,

Thank you for working on this.

- Ali

  reply	other threads:[~2022-04-04  7:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 11:55 christian.ehrhardt
2022-03-30 11:04 ` Jiang, YuX
2022-03-31 10:00   ` Christian Ehrhardt
2022-04-06  6:49     ` Christian Ehrhardt
2022-04-06  7:05       ` Jiang, YuX
2022-04-06  8:40         ` Christian Ehrhardt
2022-03-31 10:50 ` Christian Ehrhardt
2022-04-01 14:34 ` Kalesh Anakkur Purayil
2022-04-04  6:35   ` Christian Ehrhardt
2022-04-04  6:39 ` Christian Ehrhardt
2022-04-04  7:02   ` Ali Alnubani [this message]
2022-04-04  6:52 ` Ali Alnubani
2022-04-04  7:12   ` Christian Ehrhardt
2022-04-06  2:11 ` Pei Zhang
2022-04-06  6:45   ` Christian Ehrhardt

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=DM4PR12MB51672B5D787385F6529780ECDAE59@DM4PR12MB5167.namprd12.prod.outlook.com \
    --to=alialnu@nvidia.com \
    --cc=Abhishek.Marathe@microsoft.com \
    --cc=benjamin.walker@intel.com \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=ian.stokes@intel.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=juhlee@microsoft.com \
    --cc=ktraynor@redhat.com \
    --cc=pezhang@redhat.com \
    --cc=qian.q.xu@intel.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=yuan.peng@intel.com \
    --cc=zhaoyan.chen@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).