From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Qi Zhang <qi.z.zhang@intel.com>,
wenzhuo.lu@intel.com, jingjing.wu@intel.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH 1/2] app/testpmd: fix port id type
Date: Tue, 24 Apr 2018 12:23:00 +0100 [thread overview]
Message-ID: <720c6cfc-ae87-49a4-22c3-45c33f9f052b@intel.com> (raw)
In-Reply-To: <43794602-5553-384a-ccd5-63d2a4f70a37@intel.com>
On 4/24/2018 12:21 PM, Ferruh Yigit wrote:
> On 4/24/2018 6:59 AM, Qi Zhang wrote:
>> Correct couple port id from uint8_t to uint16_t.
>>
>> Fixes: f8244c6399d9 ("ethdev: increase port id range")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
>
> For Series,
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-04-24 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 5:59 [dpdk-dev] " Qi Zhang
2018-04-24 5:59 ` [dpdk-dev] [PATCH 2/2] app/testpmd: fix command token Qi Zhang
2018-04-24 11:21 ` [dpdk-dev] [dpdk-stable] [PATCH 1/2] app/testpmd: fix port id type Ferruh Yigit
2018-04-24 11:23 ` Ferruh Yigit [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=720c6cfc-ae87-49a4-22c3-45c33f9f052b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@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).