patches for DPDK stable branches
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: "Xueming(Steven) Li" <xuemingl@nvidia.com>,
	Luca Boccassi <bluca@debian.org>
Cc: dpdk stable <stable@dpdk.org>, Aaron Conole <aconole@redhat.com>,
	 "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Kevin Traynor <ktraynor@redhat.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: Re: [dpdk-stable] please help backporting some patches to stable release 20.11.2
Date: Tue, 11 May 2021 11:34:15 +0200	[thread overview]
Message-ID: <CAJFAV8y86oF7osVphTJ6jv4=O3uODP_W=77nyw1b_Pmixq1Bbg@mail.gmail.com> (raw)
In-Reply-To: <20210510224153.31477-1-xuemingl@nvidia.com>

On Tue, May 11, 2021 at 12:42 AM Xueming Li <xuemingl@nvidia.com> wrote:
> 3cd7290c16  David Marchand   ci: catch coredumps

I can provide the backport for this.

But instead:

Since Travis is almost unusable, 20.11 stable maintainers won't be
able to run non regression tests.
I would recommend backporting GHA support in 20.11.

Another thing is that the 20.11 does not have ABI checks enabled.
At the moment, backports are easy and won't break ABI, but later, once
v21.11 is out, we must be careful not to backport anything breaking
ABI.


I did the test, cherry-picking needed patches for the suggestions above.

87009585e2 - ci: hook to GitHub Actions (5 months ago) <David Marchand>
443267090e - ci: enable v21 ABI checks (5 months ago) <David Marchand>
9d620630ea - ci: fix package installation in GitHub Actions (5 months
ago) <David Marchand>
1e90d1b67b - ci: ignore APT update failure in GitHub Actions (3 months
ago) <David Marchand>
3cd7290c16 - ci: catch coredumps (10 weeks ago) <David Marchand>
aa9cb78f66 - doc: fix sphinx rtd theme import in GHA (6 weeks ago)
<David Marchand>

https://github.com/david-marchand/dpdk/actions/runs/831111482


What do you think?

-- 
David Marchand


  parent reply	other threads:[~2021-05-11  9:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210510224153.31477-1-xuemingl@nvidia.com>
2021-05-11  6:43 ` Elad Nachman
2021-05-11 11:43   ` Xueming(Steven) Li
2021-05-11  9:34 ` David Marchand [this message]
2021-05-11 10:36   ` Luca Boccassi
2021-05-11 11:25     ` David Marchand
2021-05-11 14:44   ` Aaron Conole
2021-05-11 23:41     ` Xueming(Steven) Li
2021-05-11 11:18 ` Thomas Monjalon
2021-05-13 10:18 ` [dpdk-stable] Fwd: " Ferruh Yigit

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='CAJFAV8y86oF7osVphTJ6jv4=O3uODP_W=77nyw1b_Pmixq1Bbg@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=ferruh.yigit@intel.com \
    --cc=ktraynor@redhat.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=xuemingl@nvidia.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).