From: "Yang, Zhiyong" <zhiyong.yang@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/6] fix port id type
Date: Fri, 13 Oct 2017 02:31:34 +0000 [thread overview]
Message-ID: <E182254E98A5DA4EB1E657AC7CB9BD2A8AF43DFE@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <bd004a90-9b49-1f08-1d7e-b739de1c78a0@intel.com>
Hi Ferruh,
OK, I see. I will send another patches to fix them as soon as possible.
Thanks
Zhiyong
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Friday, October 13, 2017 10:20 AM
> To: Yang, Zhiyong <zhiyong.yang@intel.com>; dev@dpdk.org;
> thomas@monjalon.net; Richardson, Bruce <bruce.richardson@intel.com>
> Subject: Re: [dpdk-dev] [PATCH 0/6] fix port id type
>
> On 10/13/2017 3:04 AM, Yang, Zhiyong wrote:
> > Hi Ferruh,
> >
> > The patch (ethdev: increase port_id range) tend to increase port id
> > range in ethdev, not eventdev, Do you mean we should change eventdev port
> id ?
> >
> > Before V2, that patchset includes eventdev port id extension.
> >
> > but Bruce reminded me about it in that patchset v2 thread and suggest
> > to send a separate patch/patchset to fix it if required. So, I didn’t touch the
> event related files after v2.
> >
> > If required, I can send eventdev port id range patch soon.
>
> Sorry I just copy-paste the command output without parsing.
>
> No we are not interested in eventdev ones, please ignore them, but in the list
> there can be still ethdev related ones, you will need to check them first.
>
> Thanks,
> ferruh
prev parent reply other threads:[~2017-10-13 2:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 9:32 Zhiyong Yang
2017-10-12 9:32 ` [dpdk-dev] [PATCH 1/6] lib/librte_ether: " Zhiyong Yang
2017-10-12 9:32 ` [dpdk-dev] [PATCH 2/6] net/bnxt: " Zhiyong Yang
2017-10-12 9:32 ` [dpdk-dev] [PATCH 3/6] net/liquidio: " Zhiyong Yang
2017-10-12 9:32 ` [dpdk-dev] [PATCH 4/6] app/pdump: " Zhiyong Yang
2017-10-12 9:32 ` [dpdk-dev] [PATCH 5/6] app/proc_info: " Zhiyong Yang
2017-10-12 9:32 ` [dpdk-dev] [PATCH 6/6] app/testpmd: " Zhiyong Yang
2017-10-12 18:03 ` [dpdk-dev] [PATCH 0/6] " Ferruh Yigit
2017-10-12 20:12 ` Ferruh Yigit
2017-10-13 2:04 ` Yang, Zhiyong
2017-10-13 2:20 ` Ferruh Yigit
2017-10-13 2:31 ` Yang, Zhiyong [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=E182254E98A5DA4EB1E657AC7CB9BD2A8AF43DFE@BGSMSX101.gar.corp.intel.com \
--to=zhiyong.yang@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--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).