From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Xiaoyun Li <xiaoyun.li@intel.com>,
xiaolong.ye@intel.com, qi.z.zhang@intel.com
Cc: beilei.xing@intel.com, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] common/iavf: update copyright
Date: Mon, 18 May 2020 19:12:16 +0100 [thread overview]
Message-ID: <ba887479-59a9-9dac-951e-0610bc2355dc@intel.com> (raw)
In-Reply-To: <9d4f46a0-c0bb-d080-cba4-bcc88844c24d@intel.com>
On 5/18/2020 11:43 AM, Ferruh Yigit wrote:
> On 5/18/2020 9:45 AM, Xiaoyun Li wrote:
>> Clarify Intel copyright and update the date to 2020.
>>
>> Fixes: 317862a4e44f ("net/iavf: replace license text with SPDX tag")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Xiaoyun Li <xiaoyun.li@intel.com>
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2020-05-18 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 8:45 [dpdk-dev] " Xiaoyun Li
2020-05-18 10:43 ` Ferruh Yigit
2020-05-18 18:12 ` 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=ba887479-59a9-9dac-951e-0610bc2355dc@intel.com \
--to=ferruh.yigit@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=xiaolong.ye@intel.com \
--cc=xiaoyun.li@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).