From: Thomas Monjalon <thomas@monjalon.net>
To: Vipin Varghese <vipin.varghese@intel.com>
Cc: dev@dpdk.org, deepak.k.jain@intel.com, nikhil.rao@intel.com,
stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] test/eventdev: update the port id to 16 bit
Date: Mon, 21 May 2018 01:17:15 +0200 [thread overview]
Message-ID: <2186577.ZmWxozCHPv@xps> (raw)
In-Reply-To: <1526407602-112993-1-git-send-email-vipin.varghese@intel.com>
15/05/2018 20:06, Vipin Varghese:
> port id in test case is update to unsigned int 16 bit, to
> prevent compilation failure when RTE_MAX_ETHPORTS port is
> set more than 255.
>
> Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
> Acked-by: Nikhil Rao <nikhil.rao@intel.com>
Fixes: fc8030eb8fe9 ("test/eventdev: add tests for eth Rx adapter APIs")
Cc: stable@dpdk.org
Applied, thanks
parent reply other threads:[~2018-05-20 23:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1526407602-112993-1-git-send-email-vipin.varghese@intel.com>]
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=2186577.ZmWxozCHPv@xps \
--to=thomas@monjalon.net \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=nikhil.rao@intel.com \
--cc=stable@dpdk.org \
--cc=vipin.varghese@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).