DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: <mohamad.noor.alim.hussin@intel.com>
Cc: <bruce.richardson@intel.com>, <david.marchand@redhat.com>,
	<tianfei.zhang@intel.com>, "stable@dpdk.org" <stable@dpdk.org>,
	Rosen Xu <rosen.xu@intel.com>, Qi Zhang <qi.z.zhang@intel.com>,
	<dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] ifpga/base/meson: fix looking for librt
Date: Mon, 30 Aug 2021 10:29:59 +0100	[thread overview]
Message-ID: <806d1b80-1611-c9d3-a507-66aeea20a24a@intel.com> (raw)
In-Reply-To: <20210722081603.42711-1-mohamad.noor.alim.hussin@intel.com>

On 7/22/2021 9:16 AM, mohamad.noor.alim.hussin@intel.com wrote:
> From: Mohamad Noor Alim Hussin <mohamad.noor.alim.hussin@intel.com>
> 
> Finding with "librt" keyword would give the output with full path of librt such
> as /usr/lib/gcc/x86_64-linux-gnu/7/../../../x86_64-linux-gnu/librt.so
> instead of -lrt in libdpdk.pc pkg-config file.
> 
> Assume find_library() will prepend "lib", thus remove "lib" from "librt"
> keyword. The output will shows as -lrt.
> 
> This will cause an issue when compile DPDK app with static library as the
> path of librt has been hard-coded in the libdpdk.pc file.
> 
> Fixes: e41856b515ce ("raw/ifpga/base: enhance driver reliability in multi-process")
> Cc: tianfei.zhang@intel.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Mohamad Noor Alim Hussin <mohamad.noor.alim.hussin@intel.com>

This patch is resent, because original patch was not in the patchwork as David
reminded.

But first patch already has acks, I am moving them here:

Acked-by: Tianfei Zhang <tianfei.zhang@intel.com>
(converted email address to all lowercase)

Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Also I can produce the same, and patch looks good to me.


But it fails to apply clearly because of the white-space differences, and this
prevents CI running.

@Mohamad, can you please send a new version rebasing on top of latest code?
Please keep the acks above in the next version commit log, since the change will
be only white-space.

Thanks,
ferruh

  reply	other threads:[~2021-08-30  9:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210630092613.70647-1-mohamad.noor.alim.hussin@intel.com>
2021-06-30 10:02 ` Xu, Rosen
2021-07-01 13:18   ` Zhang, Tianfei
2021-07-02  1:46     ` Hussin, Mohamad Noor Alim
2021-07-14  3:40       ` Zhang, Tianfei
2021-07-15  8:00         ` David Marchand
2021-07-15  8:11           ` Bruce Richardson
2021-07-22  8:16             ` mohamad.noor.alim.hussin
2021-08-30  9:29               ` Ferruh Yigit [this message]
2021-09-28  4:36               ` [dpdk-dev] [PATCH v3] " mohamad.noor.alim.hussin
2021-10-06 14:14                 ` 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=806d1b80-1611-c9d3-a507-66aeea20a24a@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mohamad.noor.alim.hussin@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=rosen.xu@intel.com \
    --cc=stable@dpdk.org \
    --cc=tianfei.zhang@intel.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).