DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Thomas Monjalon <thomas@monjalon.net>, mvarlese@suse.de
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] app/testpmd: fix DPAA shared library dependency
Date: Fri, 23 Feb 2018 10:45:56 +0530	[thread overview]
Message-ID: <9f7c6ca7-e80e-8fd1-908f-90389f5430e5@nxp.com> (raw)
In-Reply-To: <20180222225308.16972-1-thomas@monjalon.net>

On 2/23/2018 4:23 AM, Thomas Monjalon wrote:
> The dynamic link is broken for ARM platform because the dependencies
> of the DPAA PMD are not declared.
> 
> Fixes: 83c82e15e1c0 ("app/testpmd: support loopback config for DPAA")
> Cc: stable@dpdk.org
> 
> Reported-by: Marco Varlese <mvarlese@suse.de>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>

  parent reply	other threads:[~2018-02-23  5:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22 14:23 [dpdk-dev] 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     ` [dpdk-dev] [PATCH 1/2] app/testpmd: fix DPAA shared library dependency Thomas Monjalon
2018-02-22 22:53       ` [dpdk-dev] [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       ` Hemant Agrawal [this message]
2018-02-23  9:58       ` [dpdk-dev] [PATCH v2 1/2] app/testpmd: fix DPAA shared library dependency Hemant Agrawal
2018-02-23  9:58         ` [dpdk-dev] [PATCH v2 2/2] mk: fix the build dependency structure for dpaaX Hemant Agrawal
2018-03-13 23:36           ` [dpdk-dev] [dpdk-stable] " 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=9f7c6ca7-e80e-8fd1-908f-90389f5430e5@nxp.com \
    --to=hemant.agrawal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=mvarlese@suse.de \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).