From: Bruce Richardson <bruce.richardson@intel.com>
To: "Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/2] bonding fixes
Date: Fri, 26 Feb 2016 17:48:06 +0000 [thread overview]
Message-ID: <20160226174806.GF28808@bricha3-MOBL3> (raw)
In-Reply-To: <345C63BAECC1AD42A2EC8C63AFFC3ADC28128EAD@irsmsx105.ger.corp.intel.com>
On Mon, Feb 22, 2016 at 01:20:18PM +0000, Doherty, Declan wrote:
> > -----Original Message-----
> > From: Iremonger, Bernard
> > Sent: Wednesday, February 10, 2016 10:14 AM
> > To: dev@dpdk.org
> > Cc: Doherty, Declan <declan.doherty@intel.com>; Iremonger, Bernard
> > <bernard.iremonger@intel.com>
> > Subject: [PATCH 0/2] bonding fixes
> >
> > These patches fix segmentation faults which were occurring when
> > slave devices were detached before being removed from the bonding
> > device.
> > The slave devices must now be removed from the bonding device
> > before they can be detached.
> > The bonding device cannot be detached now until all slave devices
> > have been removed from it.
> >
> > Bernare Iremonger (2):
> > bonding: fix detach of bonded device
> > bonding: fix detach of bonded slave devices
> >
> > drivers/net/bonding/rte_eth_bond_api.c | 40 +++++++++++++++-----------------
> > --
> > lib/librte_ether/rte_ethdev.c | 8 +++++--
> > lib/librte_ether/rte_ethdev.h | 4 +++-
> > 3 files changed, 26 insertions(+), 26 deletions(-)
> >
> > --
> > 2.6.3
>
> Series Acked-by: Declan Doherty <declan.doherty@intel.com>
Applied to dpdk-next-net/rel_16_04
/Bruce
prev parent reply other threads:[~2016-02-26 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 10:13 Bernard Iremonger
2016-02-10 10:13 ` [dpdk-dev] [PATCH 1/2] bonding: fix detach of bonded device Bernard Iremonger
2016-02-10 10:13 ` [dpdk-dev] [PATCH 2/2] bonding: fix detach of bonded slave devices Bernard Iremonger
2016-02-22 13:20 ` [dpdk-dev] [PATCH 0/2] bonding fixes Doherty, Declan
2016-02-26 17:48 ` Bruce Richardson [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=20160226174806.GF28808@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@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).