From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Aaron Conole <aconole@redhat.com>,
David Marchand <david.marchand@redhat.com>
Cc: Luca Boccassi <bluca@debian.org>, dpdk stable <stable@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
NBU-Contact-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 23:41:47 +0000 [thread overview]
Message-ID: <BY5PR12MB43242DA932F6194C6701CE6BA1539@BY5PR12MB4324.namprd12.prod.outlook.com> (raw)
In-Reply-To: <f7tk0o55nzx.fsf@redhat.com>
> -----Original Message-----
> From: Aaron Conole <aconole@redhat.com>
> Sent: Tuesday, May 11, 2021 10:44 PM
> To: David Marchand <david.marchand@redhat.com>
> Cc: Xueming(Steven) Li <xuemingl@nvidia.com>; Luca Boccassi <bluca@debian.org>; dpdk stable <stable@dpdk.org>; Yigit, Ferruh
> <ferruh.yigit@intel.com>; NBU-Contact-Thomas Monjalon <thomas@monjalon.net>; Kevin Traynor <ktraynor@redhat.com>;
> Christian Ehrhardt <christian.ehrhardt@canonical.com>
> Subject: Re: please help backporting some patches to stable release 20.11.2
>
> David Marchand <david.marchand@redhat.com> writes:
>
> > 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.
>
> +1
>
> > 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?
>
> LGTM
Cherry-picked to 20.11 branch, CI built successfully, thanks!
https://github.com/steevenlee/dpdk/actions
next prev parent reply other threads:[~2021-05-11 23:41 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
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 [this message]
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=BY5PR12MB43242DA932F6194C6701CE6BA1539@BY5PR12MB4324.namprd12.prod.outlook.com \
--to=xuemingl@nvidia.com \
--cc=aconole@redhat.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.com \
--cc=stable@dpdk.org \
--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).