From: David Marchand <david.marchand@redhat.com>
To: Storage Performance Development Kit <spdk@lists.01.org>
Cc: Aaron Conole <aconole@redhat.com>, Brandon Lo <blo@iol.unh.edu>,
Lincoln Lavoie <lylavoie@iol.unh.edu>,
"dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>,
"ci@dpdk.org" <ci@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-ci] [SPDK] Re: [dpdklab] Re: [dpdk-dev] [CI] SPDK compilation failures @ DPDK community lab
Date: Mon, 15 Feb 2021 10:12:06 +0100 [thread overview]
Message-ID: <CAJFAV8wY4hHo0rt=gZ9Jr9qao6xuoUx40OyJyojW2mHgRfHgkg@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB4220748A0C219E31BB33B2BDEE8B9@DM6PR11MB4220.namprd11.prod.outlook.com>
On Fri, Feb 12, 2021 at 10:18 AM Zawadzki, Tomasz
<tomasz.zawadzki@intel.com> wrote:
> On SPDK side rte_net was included in default compilation with vhost component, but since vhost is disabled in the UNH lab tests with SPDK it showed up as missing. A fix for that is now submitted to SPDK:
> https://review.spdk.io/gerrit/c/spdk/spdk/+/6398
> I'll let you know when it makes it's way to the v21.01.x branch.
Rather than maintain dpdk internal dependencies on SPDK side, would it
be possible to use pkg-config?
--
David Marchand
next prev parent reply other threads:[~2021-02-15 9:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 15:21 [dpdk-ci] " Aaron Conole
2021-02-08 16:03 ` [dpdk-ci] [dpdk-dev] " Zawadzki, Tomasz
2021-02-08 16:21 ` Lincoln Lavoie
2021-02-08 17:17 ` Zawadzki, Tomasz
2021-02-09 15:13 ` Aaron Conole
2021-02-09 16:07 ` [dpdk-ci] [dpdklab] " Brandon Lo
2021-02-09 17:54 ` Brandon Lo
2021-02-11 14:02 ` Aaron Conole
2021-02-11 16:25 ` Brandon Lo
2021-02-12 9:18 ` Zawadzki, Tomasz
2021-02-12 17:39 ` Brandon Lo
2021-02-15 15:28 ` Aaron Conole
2021-02-17 16:06 ` Zawadzki, Tomasz
2021-02-18 13:58 ` Brandon Lo
2021-02-15 9:12 ` David Marchand [this message]
2021-02-15 9:56 ` [dpdk-ci] [dpdk-dev] [SPDK] Re: [dpdklab] " Nick Connolly
2021-02-15 10:15 ` David Marchand
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='CAJFAV8wY4hHo0rt=gZ9Jr9qao6xuoUx40OyJyojW2mHgRfHgkg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=blo@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=lylavoie@iol.unh.edu \
--cc=spdk@lists.01.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).