From: Thomas Monjalon <thomas@monjalon.net>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: dev@dpdk.org, Akhil Goyal <akhil.goyal@nxp.com>,
olivier.matz@6wind.com, ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH 1/2] drivers: fix shared build error for DPAA crypto
Date: Thu, 26 Oct 2017 23:06:28 +0200 [thread overview]
Message-ID: <5581759.lrYajTBS42@xps> (raw)
In-Reply-To: <297afe1c-65dd-a597-b28c-5697a3b14bf8@nxp.com>
26/10/2017 16:10, Akhil Goyal:
> On 10/26/2017 7:39 PM, Shreyansh Jain wrote:
> > Various symbols are being used by DPAA Crypto driver which were not exposed
> > from DPAA bus during initial version. This breaks the shared build.
> >
> > This patch also adds the LDLIBS line required after (cbc12b0a9) patch.
> >
> > Fixes: c3e85bdcc6e6 ("crypto/dpaa_sec: add crypto driver for NXP DPAA platform")
> > Cc: akhil.goyal@nxp.com
> >
> > Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
> >
> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Applied, thanks
prev parent reply other threads:[~2017-10-26 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 14:09 Shreyansh Jain
2017-10-26 14:09 ` [dpdk-dev] [PATCH 2/2] drivers: fix shared build error for dpaa2 event Shreyansh Jain
2017-10-26 14:10 ` [dpdk-dev] [PATCH 1/2] drivers: fix shared build error for DPAA crypto Akhil Goyal
2017-10-26 21:06 ` 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=5581759.lrYajTBS42@xps \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=olivier.matz@6wind.com \
--cc=shreyansh.jain@nxp.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 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).