DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Yang, Zhiyong" <zhiyong.yang@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] examples/l2fwd-crypto: fix port id type
Date: Thu, 19 Oct 2017 03:06:14 +0000	[thread overview]
Message-ID: <E182254E98A5DA4EB1E657AC7CB9BD2A8AF47AEB@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <20171019025657.41108-1-zhiyong.yang@intel.com>

Hi,

Sorry I miss the changes in v2.  Add it after SOB.

Zhiyong

> -----Original Message-----
> From: Yang, Zhiyong
> Sent: Thursday, October 19, 2017 10:57 AM
> To: dev@dpdk.org
> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>; Yang, Zhiyong <zhiyong.yang@intel.com>
> Subject: [PATCH v2] examples/l2fwd-crypto: fix port id type
> 
> Fix port id issues and keep variables related to port ids in consistent data type
> definition "uint16_t".
> 
> Remove unnecessary cast in the meanwhile.
> 
> Fixes: f8244c6399d9 ("ethdev: increase port id range")
> Signed-off-by: Zhiyong Yang <zhiyong.yang@intel.com>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---

Changes in V2.
Add to fix some variables data types related to port id such as "l2fwd_dst_ports", 
"dest_portid", "dst_port", " rx_port_list" , according to Pablo's comments.

  reply	other threads:[~2017-10-19  3:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18  9:50 [dpdk-dev] [PATCH] " Zhiyong Yang
2017-10-18 13:10 ` De Lara Guarch, Pablo
2017-10-19  0:55   ` Yang, Zhiyong
2017-10-19  2:56 ` [dpdk-dev] [PATCH v2] " Zhiyong Yang
2017-10-19  3:06   ` Yang, Zhiyong [this message]
2017-10-19 19:10   ` De Lara Guarch, Pablo

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=E182254E98A5DA4EB1E657AC7CB9BD2A8AF47AEB@BGSMSX101.gar.corp.intel.com \
    --to=zhiyong.yang@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=pablo.de.lara.guarch@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).