From: Luca Boccassi <bluca@debian.org>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"Chen, BoX C" <box.c.chen@intel.com>
Subject: Re: [dpdk-stable] [dpdk-dev] 19.11.4 patches review and test
Date: Thu, 27 Aug 2020 11:37:06 +0100 [thread overview]
Message-ID: <c200459a4749c990c71f8b7c5330c4924cd908e2.camel@debian.org> (raw)
In-Reply-To: <45bd96a0-b8d6-ea77-68ea-1a2d6f016051@intel.com>
On Thu, 2020-08-27 at 10:47 +0100, Burakov, Anatoly wrote:
> On 26-Aug-20 10:50 AM, Luca Boccassi wrote:
> > On Wed, 2020-08-26 at 02:30 +0000, Chen, BoX C wrote:
> > > Hi Luca,
> > > Update LTS 19.11.4 test result for Intel part. No new issue is found except known issues.
> >
> > Thank you!
> >
> > > * Intel(R) Testing
> > >
> > > # Basic Intel(R) NIC testing
> > > * PF(i40e):Passed
> > > - Exception message when starting testpmd for testing external memory. It has been fixed on 20.05.patch link: http://patches.dpdk.org/patch/66041/
> >
> > Anatoly, is it safe to backport this patch to 19.11? It applies and
> > builds cleanly when cherry-picked:
> >
> > d1c7c0cdf7ba ("vfio: map contiguous areas in one go")
>
> Hi Luca,
>
> Yes, it should be safe - at least i'm not aware of any breakages ever
> being reported so far. Thanks!
Could you please double-check that there's no other patch/change that
depends on it/that it depends on and is missing from 19.11.4-rc1? Given
we wouldn't redo the full regression run, we need to be careful
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2020-08-27 10:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 18:12 [dpdk-stable] " Luca Boccassi
2020-08-24 13:22 ` [dpdk-stable] [dpdk-dev] " Christian Ehrhardt
2020-08-24 13:25 ` Luca Boccassi
2020-08-25 9:13 ` [dpdk-stable] " Pei Zhang
2020-08-25 10:08 ` [dpdk-stable] [dpdk-dev] " Luca Boccassi
2020-08-26 2:30 ` Chen, BoX C
2020-08-26 9:50 ` Luca Boccassi
2020-08-27 9:47 ` Burakov, Anatoly
2020-08-27 10:37 ` Luca Boccassi [this message]
2020-08-27 10:57 ` Burakov, Anatoly
2020-08-27 13:23 ` Luca Boccassi
2020-08-28 4:03 ` Wang, ShougangX
2020-08-28 7:52 ` Luca Boccassi
2020-08-28 14:34 ` Govindharajan, Hariprasad
2020-08-28 15:23 ` Luca Boccassi
2020-08-30 14:36 ` Ali Alnubani
2020-08-31 9:13 ` Luca Boccassi
2020-09-01 8:30 ` [dpdk-stable] " Luca Boccassi
2020-09-01 12:32 ` [dpdk-stable] [dpdk-dev] " Christian Ehrhardt
2020-09-01 12:47 ` Bruce Richardson
2020-09-01 13:22 ` Pai G, Sunil
2020-09-01 15:10 ` Stokes, Ian
2020-09-07 14:25 ` Luca Boccassi
2021-03-18 11:54 ` Christian Ehrhardt
2021-03-18 13:36 ` Pai G, Sunil
2021-03-18 14:48 ` Ilya Maximets
2021-03-18 18:24 ` Pai G, Sunil
2021-03-22 9:49 ` Christian Ehrhardt
2021-03-22 11:41 ` Bruce Richardson
2021-03-22 11:59 ` Luca Boccassi
2021-03-22 12:25 ` Thomas Monjalon
2021-03-22 14:27 ` Christian Ehrhardt
2021-03-23 18:17 ` Thomas Monjalon
2021-03-23 18:51 ` Ilya Maximets
2021-03-24 7:44 ` Christian Ehrhardt
2021-03-24 10:28 ` Pai G, Sunil
2021-03-24 13:02 ` Christian Ehrhardt
2020-09-01 12:49 ` Luca Boccassi
2020-09-01 13:01 ` Bruce Richardson
2020-09-01 13:28 ` Bruce Richardson
2020-09-01 18:04 ` [dpdk-stable] [EXTERNAL] " Abhishek Marathe
2020-09-02 10:47 ` Luca Boccassi
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=c200459a4749c990c71f8b7c5330c4924cd908e2.camel@debian.org \
--to=bluca@debian.org \
--cc=anatoly.burakov@intel.com \
--cc=box.c.chen@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).