DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Kulasek, TomaszX" <tomaszx.kulasek@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] bond: fix check initial link status of slave
Date: Mon, 29 Jun 2015 00:31:46 +0200	[thread overview]
Message-ID: <1664963.OTYa4tBJSi@xps13> (raw)
In-Reply-To: <345C63BAECC1AD42A2EC8C63AFFC3ADC27F26410@irsmsx105.ger.corp.intel.com>

> > On Fortville NIC, link status change interrupt callback is not executed when
> > slave in bonding is (re-)started. It causes that slave's NIC is inactive even
> > if its link status is up on the start.
> > 
> > This patch invokes lsc callback, just after port's start, to check its initial
> > link status and manage properly.
> > 
> > Signed-off-by: Tomasz Kulasek <tomaszx.kulasek@intel.com>
> 
> Acked-by : Declan Doherty <declan.doherty@intel.com>

Applied, thanks

      reply	other threads:[~2015-06-28 22:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24  8:50 Tomasz Kulasek
2015-06-26  7:33 ` Doherty, Declan
2015-06-28 22:31   ` 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=1664963.OTYa4tBJSi@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=tomaszx.kulasek@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).