From: Ferruh Yigit <ferruh.yigit@intel.com>
To: alexz@att.com, dev@dpdk.org, "Ananyev,
Konstantin" <konstantin.ananyev@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>
Cc: liang-min.wang@intel.com, daniels@research.att.com
Subject: Re: [dpdk-dev] [PATCH] notify VF when PF link status changes
Date: Wed, 22 Mar 2017 14:25:42 +0000 [thread overview]
Message-ID: <ec5c031f-efdb-71ac-bca7-553f29203596@intel.com> (raw)
In-Reply-To: <1490142185-10661-1-git-send-email-alexz@att.com>
On 3/22/2017 12:23 AM, alexz@att.com wrote:
> From: Alex Zelezniak <alexz@att.com>
>
Hi Alex,
Thank you for the patch.
Can you please send a new version of the patch with a sign-off?
More details related sign-off:
http://dpdk.org/doc/guides/contributing/patches.html#commit-messages-body
Overall DPDK contribution guide can be found at:
http://dpdk.org/doc/guides/contributing/patches.html
And adding ixgbe maintainers in the mail loop helps a lot for patches
get reviewed. (already added into this mail thread)
Thanks,
ferruh
prev parent reply other threads:[~2017-03-22 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 0:23 alexz
2017-03-22 14:25 ` 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=ec5c031f-efdb-71ac-bca7-553f29203596@intel.com \
--to=ferruh.yigit@intel.com \
--cc=alexz@att.com \
--cc=daniels@research.att.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=liang-min.wang@intel.com \
--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).