patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
	David Marchand <david.marchand@redhat.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Cc: Robin Jarry <robin.jarry@6wind.com>, Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-stable] [PATCH 20.11] build: fix drivers selection without Python
Date: Wed, 16 Jun 2021 03:13:41 +0000	[thread overview]
Message-ID: <DM4PR12MB537389E7DCD0D0912B20A0E0A10F9@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <ede4ad9f49864afbb3c7d3e9eb217f27@intel.com>

Merged, thanks!

> -----Original Message-----
> From: Richardson, Bruce <bruce.richardson@intel.com>
> Sent: Tuesday, June 15, 2021 8:42 PM
> To: David Marchand <david.marchand@redhat.com>; stable@dpdk.org
> Cc: Xueming(Steven) Li <xuemingl@nvidia.com>; Robin Jarry <robin.jarry@6wind.com>; Luca Boccassi <bluca@debian.org>
> Subject: RE: [PATCH 20.11] build: fix drivers selection without Python
> 
> 
> 
> > -----Original Message-----
> > From: David Marchand <david.marchand@redhat.com>
> > Sent: Tuesday, June 15, 2021 1:22 PM
> > To: stable@dpdk.org
> > Cc: xuemingl@nvidia.com; Richardson, Bruce
> > <bruce.richardson@intel.com>; Robin Jarry <robin.jarry@6wind.com>;
> > Luca Boccassi <bluca@debian.org>
> > Subject: [PATCH 20.11] build: fix drivers selection without Python
> >
> > [ upstream commit 627c5b41bb14a1afbd1489b0fc4b8224532a823d ]
> >
> > The list of disabled drivers is built by calling list-dir-globs.py.
> >
> > But if no Python interpreter is installed, no error is reported and no
> > driver is disabled.
> >
> > Example on a minimal FreeBSD VM:
> >
> >   dpdk@freebsd:~/dpdk $ meson setup build -Ddisable_drivers=net/*
> >   ...
> >   Message:
> >   ===============
> >   Drivers Enabled
> >   ===============
> >
> >   common:
> >   	cpt, iavf, octeontx, octeontx2, sfc_efx, qat,
> >   bus:
> >   	ifpga, pci, vdev,
> >   mempool:
> >   	bucket, octeontx, octeontx2, ring, stack,
> >   net:
> >   	ark, atlantic, bond, bnxt, cxgbe, e1000, ena, enic,
> >   	failsafe, fm10k, i40e, hinic, iavf, ice, igc, ixgbe,
> >   	liquidio, null, octeontx, octeontx2, pcap, qede, ring, sfc,
> >   	thunderx, txgbe, virtio, vmxnet3,
> >   ...
> >
> >   dpdk@freebsd:~/dpdk $ cd drivers/
> >   dpdk@freebsd:~/dpdk/drivers $ ~/dpdk/buildtools/list-dir-globs.py net/*
> >   env: python3: No such file or directory
> >
> > Rely on meson internal interpreter.
> > Check return code when calling this script.
> >
> > Fixes: ab9407c3addd ("build: allow using wildcards to disable
> > drivers")
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > ---
> 
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>

      reply	other threads:[~2021-06-16  3:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 12:21 David Marchand
2021-06-15 12:41 ` Richardson, Bruce
2021-06-16  3:13   ` Xueming(Steven) Li [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=DM4PR12MB537389E7DCD0D0912B20A0E0A10F9@DM4PR12MB5373.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=robin.jarry@6wind.com \
    --cc=stable@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 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).