From: David Marchand <david.marchand@redhat.com>
To: Brandon Lo <blo@iol.unh.edu>, Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: ci@dpdk.org, dpdklab <dpdklab@iol.unh.edu>,
Aaron Conole <aconole@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [dpdk-ci] [dpdklab] Re: Please install libatomic on your systems
Date: Thu, 15 Jul 2021 10:00:48 +0200 [thread overview]
Message-ID: <CAJFAV8xiFmcos08A8zyHiT1gk3hAH8fm8wg+aenE0eFYZ8mNBw@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8ziup_Gcg06ZQtTfSo8+X=cLPmmdTB3FTZ4kz=mKPW46A@mail.gmail.com>
On Wed, Jul 7, 2021 at 8:36 PM David Marchand <david.marchand@redhat.com> wrote:
>
> On Wed, Jul 7, 2021 at 7:52 PM Brandon Lo <blo@iol.unh.edu> wrote:
> >
> > Hi David,
> >
> > I have added the dependency to all containers / virtual machines that
> > run the ABI check test.
> > Could you also point me to the correct branch to compile with this new
> > dependency installed?
>
> The main branch should pass the usual tests, compile, ut, abi.
> Adding this dependency won't change anything for current main.
>
> As for the patches requiring this update, they are from this patchset:
> http://patchwork.dpdk.org/project/dpdk/list/?series=17590
> Re-running the checks on this series should give all green flags.
>
Any update?
sfc series are blocked because of this.
--
David Marchand
next prev parent reply other threads:[~2021-07-15 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 13:34 [dpdk-ci] " David Marchand
2021-07-02 16:31 ` Lincoln Lavoie
2021-07-07 11:18 ` David Marchand
2021-07-07 12:27 ` [dpdk-ci] [dpdklab] " Lincoln Lavoie
2021-07-07 17:51 ` Brandon Lo
2021-07-07 18:36 ` David Marchand
2021-07-15 8:00 ` David Marchand [this message]
2021-07-15 16:56 ` Brandon Lo
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=CAJFAV8xiFmcos08A8zyHiT1gk3hAH8fm8wg+aenE0eFYZ8mNBw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=blo@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=lylavoie@iol.unh.edu \
--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).