DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hyong Youb Kim <hyonkim@cisco.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Declan Doherty <declan.doherty@intel.com>,
	Chas Williams <chas3@att.com>
Cc: dev@dpdk.org, Hyong Youb Kim <hyonkim@cisco.com>
Subject: [dpdk-dev] [PATCH 0/2] net/bonding: a couple minor fixes
Date: Thu, 10 Jan 2019 02:22:33 -0800	[thread overview]
Message-ID: <20190110102235.1238-1-hyonkim@cisco.com> (raw)

A couple patches for minor issues found during in-house testing. I do
not have a strong opinion on the first one, as it is just a warning
message not technically a bug. But, the second one addresses an
easy-to-reproduce crash. If someone has a better/cleaner fix, I am all
ears.

Hyong Youb Kim (2):
  net/bonding: do not set promisc on non-existent primary port
  net/bonding: avoid the next active slave going out of bound

 drivers/net/bonding/rte_eth_bond_pmd.c | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

-- 
2.16.2

             reply	other threads:[~2019-01-10 10:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 10:22 Hyong Youb Kim [this message]
2019-01-10 10:22 ` [dpdk-dev] [PATCH 1/2] net/bonding: do not set promisc on non-existent primary port Hyong Youb Kim
2019-02-09 13:16   ` Chas Williams
2019-02-21 14:38     ` Ferruh Yigit
2019-01-10 10:22 ` [dpdk-dev] [PATCH 2/2] net/bonding: avoid the next active slave going out of bound Hyong Youb Kim
2019-02-09 13:17   ` Chas Williams
     [not found]     ` <7AE31235A30B41498D1C31348DC858BD5B5329AB@IRSMSX103.ger.corp.intel.com>
2019-02-18 15:25       ` Ferruh Yigit
2019-02-20 16:28         ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit

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=20190110102235.1238-1-hyonkim@cisco.com \
    --to=hyonkim@cisco.com \
    --cc=chas3@att.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).