From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Tom Barbette <barbette@kth.se>, dev@dpdk.org
Cc: thomas@monjalon.net, arybchenko@solarflare.com
Subject: Re: [dpdk-dev] [PATCH v2] reta_query: Doc requirements on reta_conf
Date: Fri, 5 Apr 2019 14:44:50 +0100 [thread overview]
Message-ID: <20c55166-b376-3e94-9053-4e84722507e1@intel.com> (raw)
Message-ID: <20190405134450.1rnKDx4oPSudRQJgzJ74tSWzPoxo6QtbdlA-Zih_6gw@z> (raw)
In-Reply-To: <20190405131337.32589-1-barbette@kth.se>
On 4/5/2019 2:13 PM, Tom Barbette wrote:
> Clarify the fact that mask bits should be set in rte_eth_reta_query.
>
> v2:
> - Change documentation string as suggested by Ferruh
>
> Signed-off-by: Tom Barbette <barbette@kth.se>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-04-05 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 13:13 Tom Barbette
2019-04-05 13:13 ` Tom Barbette
2019-04-05 13:44 ` Ferruh Yigit [this message]
2019-04-05 13:44 ` 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=20c55166-b376-3e94-9053-4e84722507e1@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=barbette@kth.se \
--cc=dev@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).