patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Chas Williams <3chas3@gmail.com>, Radu Nicolau <radu.nicolau@intel.com>
Cc: dev@dpdk.org, Declan Doherty <declan.doherty@intel.com>,
	Chas Williams <chas3@att.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/bonding: fix invalid port id error
Date: Fri, 20 Jul 2018 16:12:43 +0100	[thread overview]
Message-ID: <0f555297-ec59-d295-babd-a318e3990138@intel.com> (raw)
In-Reply-To: <CAG2-GkmZQsjcqaQb4PW6ndwmU6a_nk-SON5LRXXPMozeB8Qu0g@mail.gmail.com>

On 7/19/2018 6:45 PM, Chas Williams wrote:
> This seems fine.  The bond PMD seems to call back into itself early.
> 
> On Wed, Jul 18, 2018 at 7:19 AM Radu Nicolau <radu.nicolau@intel.com> wrote:
> 
>> setting up the bonding options before calling rte_eth_dev_probing_finish
>> triggers an invalid port id error because of port state not set, or set
>> unused
>>
>> Fixes: fbe90cdd776c ("ethdev: add probing finish function")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
>>
> 
> Signed-off-by: Chas Williams <chas3@att.com>

Signed-off-by replaced with:
Acked-by: Chas Williams <chas3@att.com>

If intention was really sign-off, please let me know

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

      reply	other threads:[~2018-07-20 15:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 11:12 [dpdk-stable] " Radu Nicolau
2018-07-19 17:45 ` [dpdk-stable] [dpdk-dev] " Chas Williams
2018-07-20 15:12   ` 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=0f555297-ec59-d295-babd-a318e3990138@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=radu.nicolau@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).