From: Konstantin Ananyev <konstantin.ananyev@intel.com>
To: dev@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCHv2 0/4] fix for 2 consecutive rte_eth_dev_start() can cause a SIGSEGV
Date: Mon, 9 Jun 2014 18:26:13 +0100 [thread overview]
Message-ID: <1402334777-27379-1-git-send-email-konstantin.ananyev@intel.com> (raw)
Konstantin Ananyev (4):
e1000: do not release queue on alloc error
igb/ixgbe: reset queue pointers after releasing
ethdev: fix compiler warning on PMD_DEBUG_TRACE formats
ethdev: prevent from starting/stopping already started/stopped
v2 changes:
Split one patch into series of 4.
lib/librte_ether/rte_ethdev.c | 29 ++++++++++++++++++++++++-----
lib/librte_pmd_e1000/em_rxtx.c | 1 -
lib/librte_pmd_e1000/igb_rxtx.c | 5 +++--
lib/librte_pmd_ixgbe/ixgbe_rxtx.c | 8 ++++++--
4 files changed, 33 insertions(+), 10 deletions(-)
--
1.8.3.1
next reply other threads:[~2014-06-09 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 17:26 Konstantin Ananyev [this message]
2014-06-09 17:26 ` [dpdk-dev] [PATCHv2 1/4] e1000: do not release queue on alloc error Konstantin Ananyev
2014-06-09 17:26 ` [dpdk-dev] [PATCHv2 2/4] igb/ixgbe: reset queue pointers after releasing Konstantin Ananyev
2014-06-09 17:26 ` [dpdk-dev] [PATCHv2 3/4] ethdev: prevent from starting/stopping already started/stopped device Konstantin Ananyev
2014-06-09 17:26 ` [dpdk-dev] [PATCHv2 4/4] ethdev: fix compiler warning on PMD_DEBUG_TRACE formats Konstantin Ananyev
2014-06-11 10:06 ` [dpdk-dev] [PATCHv2 0/4] fix for 2 consecutive rte_eth_dev_start() can cause a SIGSEGV Thomas Monjalon
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=1402334777-27379-1-git-send-email-konstantin.ananyev@intel.com \
--to=konstantin.ananyev@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).