dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Luca Boccassi <bluca@debian.org>
Cc: thomas@monjalon.net, dev@dpdk.org, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH 00/10] enhance meson summary - list disabled components
Date: Tue, 18 Jun 2019 14:18:34 +0100	[thread overview]
Message-ID: <20190618131834.GA693@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <269c69717335629bc9d5bfbc9864fb596412ae15.camel@debian.org>

On Wed, Jun 05, 2019 at 09:39:07PM +0100, Luca Boccassi wrote:
> On Wed, 2019-06-05 at 21:22 +0100, Bruce Richardson wrote:
> > After using meson to configure a build, we output a brief list of all
> > components that are enabled. However, of more use to most users is a
> > list of what is not being enabled, so that they can look for gaps and
> > see about fixing those gaps, e.g. by installing driver dependencies.
> > 
> > This patchset adds such a printout at the end, but to make things
> > easier, it also adds support for drivers adding a reason why they not
> > being built, e.g. unsupported platform, or missing software
> > dependency.
> 
> Series-acked-by: Luca Boccassi <bluca@debian.org>
> 
Ping on this patchset. It's acked almost 2 weeks now, so can it be merged?
[to get it off my "list-of-stuff-to-track"]

/Bruce

  reply	other threads:[~2019-06-18 13:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 20:22 [dpdk-dev] [PATCH 00/10] enhance meson summary - list disabled components Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 01/10] build: print list of disabled components for meson build Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 02/10] lib: add reasons for components being disabled Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 03/10] drivers/bus: " Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 04/10] drivers/common: " Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 05/10] drivers/compress: " Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 06/10] drivers/crypto: " Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 07/10] drivers/event: " Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 08/10] drivers/mempool: " Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 09/10] drivers/net: " Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 10/10] drivers/raw: " Bruce Richardson
2019-06-05 20:39 ` [dpdk-dev] [PATCH 00/10] enhance meson summary - list disabled components Luca Boccassi
2019-06-18 13:18   ` Bruce Richardson [this message]
2019-07-02 21:21   ` Thomas Monjalon

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=20190618131834.GA693@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@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).