patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Gaëtan Rivet" <gaetan.rivet@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] pci: remove duplicated symbol from map file
Date: Thu, 15 Mar 2018 18:21:18 +0100	[thread overview]
Message-ID: <20180315172118.5zjod2ue2zxl7eqg@bidouze.vm.6wind.com> (raw)
In-Reply-To: <20180315164854.101533-1-ferruh.yigit@intel.com>

Hi Ferruh,

On Thu, Mar 15, 2018 at 04:48:54PM +0000, Ferruh Yigit wrote:
> Remove duplicated symbol rte_pci_device_name from .map file.
> 
> Also sort the map file to be able to detect any possible duplication
> easier in the future.
> 
> Fixes: 0e3ef055bee5 ("pci: fix namespace prefix of new functions")
> Cc: stable@dpdk.org
> 

Acked-by: Gaetan Rivet <gaetan.rivet@6wind.com>

> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
>  lib/librte_pci/rte_pci_version.map | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/lib/librte_pci/rte_pci_version.map b/lib/librte_pci/rte_pci_version.map
> index 15d93d95c..c0280277b 100644
> --- a/lib/librte_pci/rte_pci_version.map
> +++ b/lib/librte_pci/rte_pci_version.map
> @@ -3,12 +3,11 @@ DPDK_17.11 {
>  
>  	eal_parse_pci_BDF;
>  	eal_parse_pci_DomBDF;
> -	rte_pci_addr_cmp;
> -	rte_pci_addr_parse;
> -	rte_pci_device_name;
>  	pci_map_resource;
>  	pci_unmap_resource;
>  	rte_eal_compare_pci_addr;
> +	rte_pci_addr_cmp;
> +	rte_pci_addr_parse;
>  	rte_pci_device_name;
>  
>  	local: *;
> -- 
> 2.13.6
> 

-- 
Gaëtan Rivet
6WIND

  reply	other threads:[~2018-03-15 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 16:48 Ferruh Yigit
2018-03-15 17:21 ` Gaëtan Rivet [this message]
2018-03-22 16:35   ` 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=20180315172118.5zjod2ue2zxl7eqg@bidouze.vm.6wind.com \
    --to=gaetan.rivet@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).