From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Yaroslav Brustinov <ybrustin@cisco.com>,
thomas@monjalon.net, arybchenko@solarflare.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] librte_ethdev: Fix typo in error message of invalid nb_rx_desc or nb_tx_desc
Date: Tue, 11 Dec 2018 16:42:49 +0000 [thread overview]
Message-ID: <47ce03df-a8ae-7de9-b474-9179477f7fac@intel.com> (raw)
In-Reply-To: <1543830844-30343-1-git-send-email-ybrustin@cisco.com>
On 12/3/2018 9:54 AM, Yaroslav Brustinov wrote:
> Signed-off-by: Yaroslav Brustinov <ybrustin@cisco.com>
Updated commit log as following:
ethdev: fix typo in error message in queue setup
'=' should be '>=" for '[rt]x_desc_lim.nb_min' check.
Fixes: 386c993e95f1 ("ethdev: add a missing sanity check for Tx queue setup")
Fixes: 80a1deb4c77a ("ethdev: add API to retrieve queue information")
Cc: stable@dpdk.org
Signed-off-by: Yaroslav Brustinov <ybrustin@cisco.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-12-11 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 9:54 Yaroslav Brustinov
2018-12-11 16:42 ` Ferruh Yigit [this message]
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=47ce03df-a8ae-7de9-b474-9179477f7fac@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
--cc=ybrustin@cisco.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).