patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>, dev@dpdk.org
Cc: Yongseok Koh <yskoh@mellanox.com>,
	Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	ivan.boule@6wind.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 2/2] app/testpmd: fix RSS structure initialisation
Date: Fri, 20 Oct 2017 12:46:35 -0700	[thread overview]
Message-ID: <d96a0da0-3daf-a332-3c18-96a9451c177b@intel.com> (raw)
In-Reply-To: <8b28426c813b6811a15ee18d51d44dae748b04c8.1507896510.git.nelio.laranjeiro@6wind.com>

On 10/13/2017 5:09 AM, Nelio Laranjeiro wrote:
> Struct rss_conf.rss_key_len is not initialised forcing the user to verify
> the rss_conf.rss_key pointer to know if the key is present or not.
> rss_conf.rss_key_len should have a valid length according to the size of
> the rss_key pointed.
> 
> Fixes: 560e02ee5237 ("app/testpmd: configure RSS without restart")
> Cc: ivan.boule@6wind.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
> Acked-by: Yongseok Koh <yskoh@mellanox.com>
> ---
>  app/test-pmd/cmdline.c      | 2 +-
>  drivers/net/mlx5/mlx5_rss.c | 2 +-

Hi Nelio,

Can you please separate test-pmd and driver patch please?

Thanks,
ferruh

  reply	other threads:[~2017-10-20 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1508757360.git.nelio.laranjeiro@6wind.com>
     [not found] ` <cover.1508750504.git.nelio.laranjeiro@6wind.com>
     [not found]   ` <b014d4116d1fe8ce46a641f00e7a2a8ac8b9e61f.1507896510.git.nelio.laranjeiro@6wind.com>
2017-10-13 12:09     ` Nelio Laranjeiro
2017-10-20 19:46       ` Ferruh Yigit [this message]
2017-10-23  9:45     ` [dpdk-stable] [PATCH 2/3] " Nelio Laranjeiro
2017-10-23 11:17   ` [dpdk-stable] [PATCH v3 " Nelio Laranjeiro

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=d96a0da0-3daf-a332-3c18-96a9451c177b@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=ivan.boule@6wind.com \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=stable@dpdk.org \
    --cc=yskoh@mellanox.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).