From: Thomas Monjalon <thomas@monjalon.net>
To: pbhagavatula@marvell.com
Cc: dev@dpdk.org, bruce.richardson@intel.com, bluca@debian.org,
jerinj@marvell.com
Subject: Re: [dpdk-dev] [PATCH] event/octeontx2: add libatomic dependency for 32-bit clang
Date: Thu, 04 Jul 2019 16:49:37 +0200 [thread overview]
Message-ID: <2198733.D4WsMfkeW0@xps> (raw)
In-Reply-To: <20190704085935.3328-1-pbhagavatula@marvell.com>
04/07/2019 10:59, pbhagavatula@marvell.com:
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> When compiling with clang on 32-bit platforms, we are missing
> copies of 64-bit atomic functions. We can solve this by linking
> against libatomic for the drivers and libs which need those
> atomic ops.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Applied, thanks
prev parent reply other threads:[~2019-07-04 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 8:59 pbhagavatula
2019-07-04 14:49 ` 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=2198733.D4WsMfkeW0@xps \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.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).