From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: stable@dpdk.org, dev@dpdk.org, mvarlese@suse.de, yskoh@mellanox.com
Subject: Re: [dpdk-stable] [PATCH v2 2/2] mk: fix the build dependency structure for dpaaX
Date: Wed, 14 Mar 2018 00:36:47 +0100 [thread overview]
Message-ID: <4896542.TQVVVNK1aY@xps> (raw)
In-Reply-To: <1519379883-26287-2-git-send-email-hemant.agrawal@nxp.com>
23/02/2018 10:58, Hemant Agrawal:
> This patch fixes the build dependency of various
> dpaaX components, when the dpaa or fslmc bus is disabled,
> or VFIO is disabled.
>
> Fixes: 1ee9569576f6 ("config: enable dpaaX drivers for generic ARMv8")
> Cc: stable@dpdk.org
>
> Reported-by: Yongseok Koh <yskoh@mellanox.com>
> Suggested-by: Thomas Monjalon <thomas@monjalon.net>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
I am not satisfied by handling the bus dependencies all over the place,
but I understand it is convenient.
Considering that this build system is dying (in favor of meson's one),
Series applied, thanks.
prev parent reply other threads:[~2018-03-13 23:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 14:23 DPDK 18.02 on ARM64 is broken Marco Varlese
2018-02-22 14:33 ` Gaëtan Rivet
2018-02-22 17:28 ` Hemant Agrawal
2018-02-22 20:00 ` Marco Varlese
2018-02-22 22:53 ` [PATCH 1/2] app/testpmd: fix DPAA shared library dependency Thomas Monjalon
2018-02-22 22:53 ` [PATCH 2/2] mk: clean up static link with DPAA libraries Thomas Monjalon
2018-02-23 6:25 ` Hemant Agrawal
2018-02-23 9:25 ` Thomas Monjalon
2018-02-23 10:02 ` Hemant Agrawal
2018-02-23 5:15 ` [PATCH 1/2] app/testpmd: fix DPAA shared library dependency Hemant Agrawal
2018-02-23 9:58 ` [PATCH v2 " Hemant Agrawal
2018-02-23 9:58 ` [PATCH v2 2/2] mk: fix the build dependency structure for dpaaX Hemant Agrawal
2018-03-13 23:36 ` Thomas Monjalon [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=4896542.TQVVVNK1aY@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=mvarlese@suse.de \
--cc=stable@dpdk.org \
--cc=yskoh@mellanox.com \
/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.