DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Pablo de Lara <pablo.de.lara.guarch@intel.com>, hemant.agrawal@nxp.com
Cc: dev@dpdk.org, stable@dpdk.org,
	Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] bus/fslmc: fix shared build
Date: Thu, 23 Aug 2018 11:00:29 +0530	[thread overview]
Message-ID: <9cac5632-6ad3-73b0-f381-9639072ea40e@nxp.com> (raw)
In-Reply-To: <20180821112503.34317-1-pablo.de.lara.guarch@intel.com>

On Tuesday 21 August 2018 04:55 PM, Pablo de Lara wrote:
> When building DPDK as shared library, disabling optimizations,
> the following compilation issue appears:
> 
> portal/dpaa2_hw_dpio.o: In function `dpaa2_mem_ptov':
> drivers/bus/fslmc/portal/dpaa2_hw_pvt.h:289: undefined reference to `rte_dpaa2_memsegs'
> ...
> 
> Bugzilla ID: 61
> Fixes: 365fb925d3b3 ("bus/fslmc: optimize physical to virtual address search")
> Cc: stable@dpdk.org
> 
> Reported-by: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
>   drivers/bus/fslmc/portal/dpaa2_hw_dpbp.c            | 7 +++++++
>   drivers/bus/fslmc/rte_bus_fslmc_version.map         | 1 +
>   drivers/mempool/dpaa2/dpaa2_hw_mempool.c            | 7 -------
>   drivers/mempool/dpaa2/rte_mempool_dpaa2_version.map | 1 -
>   4 files changed, 8 insertions(+), 8 deletions(-)
> 

Another patch for same issue was already submitted by Hemant a few days 
back: http://patches.dpdk.org/patch/43788/

-
Shreyansh

  reply	other threads:[~2018-08-23  5:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 11:25 Pablo de Lara
2018-08-23  5:30 ` Shreyansh Jain [this message]
2018-08-24 18:12   ` Ajit Khaparde

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=9cac5632-6ad3-73b0-f381-9639072ea40e@nxp.com \
    --to=shreyansh.jain@nxp.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=pablo.de.lara.guarch@intel.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).