DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shachar Beiser <shacharbe@mellanox.com>
To: shacharbe@mellanox.com, dev@dpdk.org
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Subject: [dpdk-dev] [PATCH v2] Adding compilation flag for fix drop action seg fault
Date: Sun, 25 Jun 2017 07:55:00 +0000	[thread overview]
Message-ID: <cover.1498376886.git.shacharbe@mellanox.com> (raw)
Message-ID: <20170625075500.w6BxEFAcY2ZOXuWmYC-11iW2cXAEXZEoxCe0CoKXzQ0@z> (raw)
In-Reply-To: <4233196997a3d8aba05b16a130ccc87f27f076bf.1498046009.git.shacharbe@mellanox.com>

Shachar Beiser (1):
  net/mlx5: fix drop action seg fault

 drivers/net/mlx5/mlx5_flow.c | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

-- 
1.8.3.1

  parent reply	other threads:[~2017-06-25  8:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 11:55 [dpdk-dev] [PATCH] net/mlx5: " Shachar Beiser
2017-06-21 13:02 ` Nélio Laranjeiro
2017-06-22  9:51   ` Ferruh Yigit
2017-06-22 11:11 ` Ferruh Yigit
2017-06-25  7:42 ` [dpdk-dev] [PATCH v2] fix drop action seg fault missing compilation flag Shachar Beiser
2017-06-25  7:42   ` [dpdk-dev] [PATCH v2] net/mlx5: fix drop action seg fault Shachar Beiser
2017-06-25  7:46     ` Shachar Beiser
2017-06-25  7:46   ` [dpdk-dev] [PATCH v2] fix drop action seg fault missing compilation flag Shachar Beiser
2017-06-25  7:53 ` Shachar Beiser [this message]
2017-06-25  7:55   ` [dpdk-dev] [PATCH v2] Adding compilation flag for fix drop action seg fault Shachar Beiser
2017-06-25  7:53 ` [dpdk-dev] [PATCH v2] net/mlx5: " Shachar Beiser
2017-06-25  7:55   ` Shachar Beiser
2017-06-26 12:28   ` Nélio Laranjeiro
2017-06-26 12:55     ` Ferruh Yigit
2017-06-26 13:41       ` Nélio Laranjeiro
2017-06-26 13:51         ` Ferruh Yigit
2017-06-26 14:12     ` 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=cover.1498376886.git.shacharbe@mellanox.com \
    --to=shacharbe@mellanox.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=nelio.laranjeiro@6wind.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).