From: Luca Boccassi <bluca@debian.org>
To: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Cc: thomas@monjalon.net, Neil Horman <nhorman@tuxdriver.com>,
ray.kinsella@intel.com
Subject: Re: [dpdk-dev] [PATCH 0/3] Add scanning for experimental symbols to meson
Date: Wed, 09 Oct 2019 09:17:02 +0100 [thread overview]
Message-ID: <04c7b55b1cf47214ddd53e693dad17067e9a2926.camel@debian.org> (raw)
In-Reply-To: <20191008143628.46054-1-bruce.richardson@intel.com>
On Tue, 2019-10-08 at 15:36 +0100, Bruce Richardson wrote:
> The meson builds were missing support for scanning experimental
> symbols
> in the .o/.a files and matching that against those tagged as
> experimental in the version file. This set adds that missing support.
>
> Bruce Richardson (3):
> check-experimental-syms: remove use of environmental var
> lib: add experimental symbols check to meson build
> drivers: process shared lib link dependencies as for libs
>
> buildtools/check-experimental-syms.sh | 2 +-
> buildtools/meson.build | 2 ++
> drivers/meson.build | 27
> +++++++++++++++++++++++++--
> lib/meson.build | 12 +++++++++++-
> 4 files changed, 39 insertions(+), 4 deletions(-)
Series-acked-by: Luca Boccassi <bluca@debian.org>
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2019-10-09 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 14:36 Bruce Richardson
2019-10-08 14:36 ` [dpdk-dev] [PATCH 1/3] check-experimental-syms: remove use of environmental var Bruce Richardson
2019-10-08 14:36 ` [dpdk-dev] [PATCH 2/3] lib: add experimental symbols check to meson build Bruce Richardson
2019-10-08 14:36 ` [dpdk-dev] [PATCH 3/3] drivers: process shared lib link dependencies as for libs Bruce Richardson
2019-10-09 8:17 ` Luca Boccassi [this message]
2019-11-09 20:23 ` [dpdk-dev] [PATCH 0/3] Add scanning for experimental symbols to meson Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2019-10-08 14:36 Bruce Richardson
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=04c7b55b1cf47214ddd53e693dad17067e9a2926.camel@debian.org \
--to=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=nhorman@tuxdriver.com \
--cc=ray.kinsella@intel.com \
--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).