From: Thomas Monjalon <thomas@monjalon.net>
To: Lei <lei.a.yao@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
nikhil.rao@intel.com, jerin.jacob@cavium.com
Subject: Re: [dpdk-dev] [PATCH] eventdev: change port_id to uint16_t
Date: Fri, 11 May 2018 11:00:32 +0200 [thread overview]
Message-ID: <2342302.sue3H7Idtu@xps> (raw)
In-Reply-To: <33b05f1b-5425-0648-d1c2-31cd01d79d67@intel.com>
10/05/2018 21:59, Ferruh Yigit:
> On 5/8/2018 3:27 PM, Lei wrote:
> > From: yao <lei.a.yao@intel.com>
> >
> > From 17.11, port_id is changed from uint8_t to uint16_t.But in eventdev,
> > it still use the old fashion. This patch fix this issue.
> >
> > Signed-off-by: Lei Yao <lei.a.yao@intel.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> This issue also cause build error when CONFIG_RTE_MAX_ETHPORTS more than 255
>
> More detail related the build error can be found at:
> https://dpdk.org/dev/patchwork/patch/39658/
Another patch was been pushed in next-eventdev:
https://dpdk.org/dev/patchwork/patch/39706/
prev parent reply other threads:[~2018-05-11 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 14:27 Lei
2018-05-10 12:58 ` Remy Horton
2018-05-10 19:59 ` Ferruh Yigit
2018-05-11 9:00 ` Thomas Monjalon [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=2342302.sue3H7Idtu@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerin.jacob@cavium.com \
--cc=lei.a.yao@intel.com \
--cc=nikhil.rao@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).