DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Chas Williams <3chas3@gmail.com>, dev@dpdk.org
Cc: declan.doherty@intel.com, Chas Williams <chas3@att.com>, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH 1/2] net/bonding: export mode 4 slave info routine
Date: Tue, 22 May 2018 11:05:56 +0100	[thread overview]
Message-ID: <80535789-2571-2de8-b3c8-db3735a38056@intel.com> (raw)
In-Reply-To: <20180517232252.19908-1-3chas3@gmail.com>

On 5/18/2018 12:22 AM, Chas Williams wrote:
> From: Chas Williams <chas3@att.com>
> 
> rte_eth_bond_8023ad_slave_info() wasn't exported in the original work.
> Useful to extract information about the current 802.3ad state.
> 
> Fixes: 46fb43683679 ("bond: add mode 4")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Chas Williams <chas3@att.com>

Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/master, thanks.

(Note, not get whole patch, only this one!)

The API seems added in 2014, not used in any internal tool and nobody complained
up until now, it seems not a popular one...

> ---
>  drivers/net/bonding/rte_pmd_bond_version.map | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/net/bonding/rte_pmd_bond_version.map b/drivers/net/bonding/rte_pmd_bond_version.map
> index ec3374b0f..cdd77df84 100644
> --- a/drivers/net/bonding/rte_pmd_bond_version.map
> +++ b/drivers/net/bonding/rte_pmd_bond_version.map
> @@ -52,3 +52,10 @@ DPDK_17.08 {
>  
>  
>  } DPDK_16.07;
> +
> +DPDK_18.08 {
> +	global:
> +
> +	rte_eth_bond_8023ad_slave_info;
> +
> +}:
s/}:/ DPDK_17.08;/

Fixed while applying.

      parent reply	other threads:[~2018-05-22 10:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 23:22 [dpdk-dev] " Chas Williams
2018-05-17 23:22 ` [dpdk-dev] [PATCH 2/2] net/bonding: always update bonding link status Chas Williams
2018-06-14 17:05   ` Ferruh Yigit
2018-05-22 10:05 ` Ferruh Yigit [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=80535789-2571-2de8-b3c8-db3735a38056@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=3chas3@gmail.com \
    --cc=chas3@att.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --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).