From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] bus/dpaa/base: fix build when assert enabled
Date: Fri, 22 Dec 2017 12:35:27 +0530 [thread overview]
Message-ID: <a1550f2c-5e0e-ee37-61c5-c02a5cf8afcf@nxp.com> (raw)
In-Reply-To: <20171222021316.52433-1-ferruh.yigit@intel.com>
On Friday 22 December 2017 07:43 AM, Ferruh Yigit wrote:
> Enabling CONFIG_RTE_ENABLE_ASSERT cause build error because some fields
> protected by RTE_LIBRTE_DPAA_HWDEBUG macro accessed within DPAA_ASSERT.
>
> All DPAA_ASSERT macro usage causing the build error wrapped with
> RTE_LIBRTE_DPAA_HWDEBUG macro.
>
> Fixes: f38f61e982f8 ("bus/dpaa: add BMAN hardware interfaces")
> Fixes: c47ff048b99a ("bus/dpaa: add QMAN driver core routines")
> Cc: shreyansh.jain@nxp.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
>
In near future, I will find a better way to have HWDEBUG. But, until
that time, we can go with this patch.
Ferruh, thanks for doing this.
Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
next prev parent reply other threads:[~2017-12-22 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 2:13 Ferruh Yigit
2017-12-22 7:05 ` Shreyansh Jain [this message]
2017-12-23 15:23 ` 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=a1550f2c-5e0e-ee37-61c5-c02a5cf8afcf@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.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).