From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Raslan Darawsheh <rasland@mellanox.com>, grive@u256.net
Cc: thomas@monjalon.net, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] net/failsafe: fix reported hash key size in device info
Date: Wed, 5 Feb 2020 09:44:58 +0000 [thread overview]
Message-ID: <0a092364-b436-3eee-743b-bc57f9cbb583@intel.com> (raw)
In-Reply-To: <1580829051-2559-1-git-send-email-rasland@mellanox.com>
On 2/4/2020 3:10 PM, Raslan Darawsheh wrote:
> Hash key size is missing from reported device info.
> This fills the hash key size in device info.
>
> Fixes: 4586be37 ("net/failsafe: fix reported device info")
> Cc: stable@dpdk.org
>
> Signed-off-by: Raslan Darawsheh <rasland@mellanox.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2020-02-05 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:10 Raslan Darawsheh
2020-02-05 9:44 ` Ferruh Yigit [this message]
[not found] <1580823780-2367-1-git-send-email-rasland@mellanox.com>
2020-02-04 13:43 ` Raslan Darawsheh
2020-02-04 15:09 ` 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=0a092364-b436-3eee-743b-bc57f9cbb583@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=grive@u256.net \
--cc=rasland@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).