From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
david.marchand@redhat.com
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 8/10/2020
Date: Fri, 09 Oct 2020 19:30:21 +0200 [thread overview]
Message-ID: <2396099.9Jxe7cSSZ7@thomas> (raw)
In-Reply-To: <20201009095647.53b65266@hermes.local>
09/10/2020 18:56, Stephen Hemminger:
> On Thu, 8 Oct 2020 13:54:50 +0100
> Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
> > * The series to update the terms/language are still in the backlog
> > * They are not passing the CI, needs attention
>
> Who is addressing this?
> I don't see any failures listed in the patchwork CI results.
I can see a CI failure in this patchset:
https://patches.dpdk.org/patch/78423/
It seems to be this error:
EAL: FATAL: Invalid 'command line' arguments.
prev parent reply other threads:[~2020-10-09 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 12:54 Ferruh Yigit
2020-10-08 14:47 ` Ferruh Yigit
2020-10-09 16:56 ` Stephen Hemminger
2020-10-09 17:30 ` Thomas Monjalon [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=2396099.9Jxe7cSSZ7@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stephen@networkplumber.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).