From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
Subject: Re: [dpdk-dev] [PATCH] app/test: allow building with bonding net driver disabled
Date: Mon, 11 May 2020 21:42:39 +0200 [thread overview]
Message-ID: <3731714.e99z0qppnp@thomas> (raw)
In-Reply-To: <d2b197f8-2eaf-53b3-41f2-ec378af1d88a@partner.samsung.com>
04/05/2020 21:26, Lukasz Wojciechowski:
> W dniu 01.05.2020 o 17:05, Bruce Richardson pisze:
> > The autotest application build was partially enabled for building with
> > the net/bond driver disabled, but a number of items were missed, leading
> > to build errors when the driver was disabled, e.g. by simply doing
> > "-Ddisable_drivers=net/*" when calling meson.
> >
> > ../app/test/test_link_bonding.c:25:10: fatal error: rte_eth_bond.h: \
> > No such file or directory
> >
> > With this fix in place, it's possible to build DPDK with meson with all
> > non-bus, non-mempool drivers disabled i.e. using meson option
> >
> > -Ddisable_drivers=baseband/*,compress/*,crypto/*,event/*,net/*,raw/*,vdpa/*
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > ---
> * confirmed issue without patch and build flag: -Ddisable_drivers=net/*
> fails to build
> * with patch applied test app still builds without flags
> * with patch applied test app builds with
> -Ddisable_drivers=baseband/*,compress/*,crypto/*,event/*,net/*,raw/*,vdpa/*
>
> Acked-by: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
> Tested-by: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
Applied, thanks
prev parent reply other threads:[~2020-05-11 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200501151113eucas1p11fc2a00e07522e5a29e1918532a1bee8@eucas1p1.samsung.com>
2020-05-01 15:05 ` Bruce Richardson
2020-05-04 19:26 ` Lukasz Wojciechowski
2020-05-11 19:42 ` 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=3731714.e99z0qppnp@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=l.wojciechow@partner.samsung.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).