From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, robin.jarry@6wind.com, amo@semihalf.com, bluca@debian.org
Subject: Re: [dpdk-dev] [PATCH v5] build: allow using wildcards to disable drivers
Date: Thu, 06 Feb 2020 03:26:09 +0100 [thread overview]
Message-ID: <5567706.UjTJXf6HLC@xps> (raw)
In-Reply-To: <20200127142822.23068-1-bruce.richardson@intel.com>
27/01/2020 15:28, Bruce Richardson:
> Rather than having to explicitly list each and every driver to disable in a
> build, we can use a small python script and the python glob library to
> expand out the wildcards. This means that we can configure meson using e.g.
>
> meson -Ddisable_drivers=crypto/*,event/* build
>
> to do a build omitting all the crypto and event drivers. Explicitly
> specified drivers e.g. net/i40e, work as before, and can be mixed with
> wildcarded drivers as required.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> Reviewed-by: Robin Jarry <robin.jarry@6wind.com>
> Acked-by: Luca Boccassi <bluca@debian.org>
Applied, thanks
prev parent reply other threads:[~2020-02-06 2:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 17:37 [dpdk-dev] [PATCH] build: allow using wildcards to disable drivers Bruce Richardson
2020-01-20 18:59 ` Thomas Monjalon
2020-01-21 9:11 ` Robin Jarry
2020-01-21 10:17 ` Bruce Richardson
2020-01-21 10:13 ` Bruce Richardson
2020-01-21 11:12 ` [dpdk-dev] [PATCH v2] " Bruce Richardson
2020-01-21 13:22 ` Robin Jarry
2020-01-21 13:37 ` Bruce Richardson
2020-01-21 13:48 ` Robin Jarry
2020-01-24 10:32 ` [dpdk-dev] [PATCH v3] " Bruce Richardson
2020-01-24 12:28 ` Robin Jarry
2020-01-24 14:57 ` Richardson, Bruce
2020-01-24 15:10 ` [dpdk-dev] [PATCH v4] " Bruce Richardson
2020-01-24 15:34 ` Robin Jarry
2020-01-27 11:26 ` Andrzej Ostruszka
2020-01-27 12:15 ` Bruce Richardson
2020-01-27 12:12 ` Luca Boccassi
2020-01-27 14:28 ` [dpdk-dev] [PATCH v5] " Bruce Richardson
2020-02-06 2:26 ` 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=5567706.UjTJXf6HLC@xps \
--to=thomas@monjalon.net \
--cc=amo@semihalf.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=robin.jarry@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.