DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: Shachar Beiser <shacharbe@mellanox.com>
Cc: dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 3/3] net/mlx5: fix interrupt enable return value
Date: Mon, 4 Sep 2017 17:24:15 +0200	[thread overview]
Message-ID: <20170904152414.iazza25sj2eoy7et@localhost> (raw)
In-Reply-To: <ea3be92578b17b0310d4539a7f0c55cf403d06bb.1504525643.git.shacharbe@mellanox.com>

On Mon, Sep 04, 2017 at 11:48:47AM +0000, Shachar Beiser wrote:
> Fixes: 3c7d44af252a ("net/mlx5: support user space Rx interrupt event")

It should fix commit e1016cb733 ("net/mlx5: fix Rx interrupts management")

> Cc: stable@dpdk.org
> 
> Signed-off-by: Shachar Beiser <shacharbe@mellanox.com>
> ---
>  drivers/net/mlx5/mlx5_rxq.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/mlx5/mlx5_rxq.c b/drivers/net/mlx5/mlx5_rxq.c
> index 437dc02..24887fb 100644
> --- a/drivers/net/mlx5/mlx5_rxq.c
> +++ b/drivers/net/mlx5/mlx5_rxq.c
> @@ -1330,7 +1330,7 @@
>  	struct priv *priv = mlx5_get_priv(dev);
>  	struct rxq *rxq = (*priv->rxqs)[rx_queue_id];
>  	struct rxq_ctrl *rxq_ctrl = container_of(rxq, struct rxq_ctrl, rxq);
> -	int ret;
> +	int ret = 0;
>  
>  	if (!rxq || !rxq_ctrl->channel) {
>  		ret = EINVAL;
> -- 
> 1.8.3.1
> 

-- 
Nélio Laranjeiro
6WIND

  reply	other threads:[~2017-09-04 15:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04 11:48 [dpdk-dev] [PATCH 1/3] net/mlx5: replace network to host macros Shachar Beiser
2017-09-04 11:48 ` [dpdk-dev] [PATCH 2/3] net/mlx5: fix TSO MLNX OFED 3.3 verification Shachar Beiser
2017-09-04 15:15   ` Nélio Laranjeiro
2017-09-04 11:48 ` [dpdk-dev] [PATCH 3/3] net/mlx5: fix interrupt enable return value Shachar Beiser
2017-09-04 15:24   ` Nélio Laranjeiro [this message]
2017-09-05  9:04     ` Shachar Beiser
2017-09-04 15:14 ` [dpdk-dev] [PATCH 1/3] net/mlx5: replace network to host macros Nélio Laranjeiro
2017-09-05  9:05   ` Shachar Beiser
2017-09-05 13:04 ` [dpdk-dev] [PATCH v2 " Shachar Beiser
2017-09-05 13:41   ` Nélio Laranjeiro
2017-09-05 13:04 ` [dpdk-dev] [PATCH v2 2/3] net/mlx5: fix TSO MLNX OFED 3.3 verification Shachar Beiser
2017-09-05 13:41   ` Nélio Laranjeiro
2017-09-14 13:43   ` [dpdk-dev] [PATCH v3 1/2] net/mlx5: replace network to host macros Shachar Beiser
2017-09-15 20:50     ` Yongseok Koh
2017-09-18  9:47       ` Shachar Beiser
2017-09-14 13:43   ` [dpdk-dev] [PATCH v3 2/2] net/mlx5: fix TSO MLNX OFED 3.3 verification Shachar Beiser
2017-09-17 10:42     ` [dpdk-dev] [PATCH v4 1/2] net/mlx5: replace network to host macros Shachar Beiser
2017-09-18 17:59       ` Yongseok Koh
2017-09-19  6:30       ` Nélio Laranjeiro
2017-09-17 10:42     ` [dpdk-dev] [PATCH v4 2/2] net/mlx5: fix TSO MLNX OFED 3.3 verification Shachar Beiser
2017-09-18 17:52       ` Yongseok Koh
2017-09-22 18:02         ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2017-09-05 13:04 ` [dpdk-dev] [PATCH v2 3/3] net/mlx5: fix interrupt enable return value Shachar Beiser
2017-09-05 13:27   ` Adrien Mazarguil
2017-09-06 10:54     ` Shachar Beiser

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=20170904152414.iazza25sj2eoy7et@localhost \
    --to=nelio.laranjeiro@6wind.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=shacharbe@mellanox.com \
    --cc=stable@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).