From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Cc: Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH] ethdev: increase length device internal name
Date: Tue, 10 Oct 2017 00:14:49 +0100 [thread overview]
Message-ID: <c6b9b875-2d8a-c7c2-36e5-ed1cc3cd5903@intel.com> (raw)
In-Reply-To: <40111fb2-af2a-6015-9dab-37a59f4e5894@intel.com>
On 10/10/2017 12:12 AM, Ferruh Yigit wrote:
> On 9/27/2017 10:23 AM, Stephen Hemminger wrote:
>> Allow sufficicent space for UUID in string form (36+1).
>> Needed to use UUID with Hyper-V. This was in deprecation notice
>> for previous release and make it so in 17.11.
>>
>> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
(deprecation notice fixed while applying)
prev parent reply other threads:[~2017-10-09 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 9:23 Stephen Hemminger
2017-10-09 23:12 ` Ferruh Yigit
2017-10-09 23:14 ` 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=c6b9b875-2d8a-c7c2-36e5-ed1cc3cd5903@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.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).