From: Bruce Richardson <bruce.richardson@intel.com>
To: agupta3@marvell.com
Cc: Harman Kalra <hkalra@marvell.com>, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 1/1] net/octeontx: fix meson build for disabled octeontx drivers
Date: Wed, 4 Mar 2020 13:49:47 +0000 [thread overview]
Message-ID: <20200304134947.GA285@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <1583300824-23635-1-git-send-email-agupta3@marvell.com>
On Wed, Mar 04, 2020 at 11:17:04AM +0530, agupta3@marvell.com wrote:
> From: Amit Gupta <agupta3@marvell.com>
>
> Add a condition to check if octeontx drivers are disabled.
> octeontx drivers are built only if dependent drivers i.e.
> ethdev, mempool and common/octeontx are enabled.
>
> Bugzilla ID: 387
>
> Fixes: 7f615033d64f ("drivers/net: build Cavium NIC PMDs with meson")
>
> Signed-off-by: Amit Gupta <agupta3@marvell.com>
Reviewed-by: Bruce Richardson <bruce.richardson@intel.com>
next prev parent reply other threads:[~2020-03-04 13:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 7:47 [dpdk-dev] [PATCH] net/octeontx: meson build fix if octeontx drivers are disabled agupta3
2020-02-17 9:54 ` David Marchand
2020-02-19 4:34 ` [dpdk-dev] [EXT] " Amit Gupta
2020-02-17 10:48 ` [dpdk-dev] " Bruce Richardson
2020-02-19 4:32 ` [dpdk-dev] [EXT] " Amit Gupta
2020-03-02 6:31 ` [dpdk-dev] [PATCH v2 1/1] net/octeontx: fix meson build for disabled octeontx drivers agupta3
2020-03-02 10:53 ` Bruce Richardson
2020-03-03 3:10 ` [dpdk-dev] [EXT] " Amit Gupta
2020-03-03 11:17 ` Bruce Richardson
2020-03-04 5:47 ` Amit Gupta
2020-03-04 5:47 ` [dpdk-dev] [PATCH v3 " agupta3
2020-03-04 13:49 ` Bruce Richardson [this message]
2020-04-05 11:57 ` Jerin Jacob
2020-04-06 10:03 ` Harman Kalra
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=20200304134947.GA285@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=agupta3@marvell.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.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).