From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, "Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH] build: print out dependency names for clarity
Date: Wed, 23 Oct 2019 16:40:28 +0200 [thread overview]
Message-ID: <2151079.TrWVs4AE6D@xps> (raw)
In-Reply-To: <364d7c84-9fbd-32fb-5204-abf3733c5386@intel.com>
18/10/2019 18:54, Burakov, Anatoly:
> On 19-Sep-19 4:07 PM, Bruce Richardson wrote:
> > To help developers to get the correct dependency name e.g. when creating a
> > new example that depends on a specific component, print out the dependency
> > name for each lib/driver as it is processed.
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > ---
>
> Very nice change, +1!
>
> Tested-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied, thanks
It makes meson processing very verbose.
Is there way to filter meson messages?
next prev parent reply other threads:[~2019-10-23 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 15:07 [dpdk-dev] [PATCH] build: print out dependency names for clarity Bruce Richardson
2019-10-18 16:54 ` Burakov, Anatoly
2019-10-23 14:40 ` Thomas Monjalon [this message]
2019-10-23 15:12 ` 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=2151079.TrWVs4AE6D@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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.