From: Stephen Hemminger <stephen@networkplumber.org>
To: Rami Rosen <ramirose@gmail.com>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, wei.dai@intel.com
Subject: Re: [dpdk-dev] [PATCH] ethdev: use correct method name in ethdev header file
Date: Tue, 12 Mar 2019 10:40:05 -0700 [thread overview]
Message-ID: <20190312104005.1fea0600@shemminger-XPS-13-9360> (raw)
In-Reply-To: <20190312160742.10724-1-ramirose@gmail.com>
On Tue, 12 Mar 2019 18:07:42 +0200
Rami Rosen <ramirose@gmail.com> wrote:
> This patch fixes rte_ethdev header file to use the correct method name,
> namely to use rte_eth_dev_info_get() instead of
> rte_eth_dev_infos_get().
>
> Fixes: a4996bd89c42 ("ethdev: new Rx/Tx offloads API")
> Fixes: 4f5701f28bd4 ("examples: fix RSS hash function configuration")
>
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
Reviewed-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2019-03-12 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 16:07 Rami Rosen
2019-03-12 17:40 ` Stephen Hemminger [this message]
2019-03-19 18:43 ` Ferruh Yigit
2019-03-19 18:43 ` 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=20190312104005.1fea0600@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ramirose@gmail.com \
--cc=wei.dai@intel.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).