From: Thomas Monjalon <thomas@monjalon.net>
To: Lee Daly <lee.daly@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
chaozhu@linux.vnet.ibm.com, remy.horton@intel.com,
orika@mellanox.com, bruce.richardson@intel.com,
pablo.de.lara.guarch@intel.com, radu.nicolau@intel.com,
tomasz.kantecki@intel.com
Subject: Re: [dpdk-dev] [PATCH] examples/l3fwd: update copyright and license
Date: Thu, 08 Feb 2018 22:47:24 +0100 [thread overview]
Message-ID: <2998814.o19V8NsUOD@xps> (raw)
In-Reply-To: <c26a0088-b271-e695-43ee-d68b50427e54@intel.com>
07/02/2018 17:15, Ferruh Yigit:
> On 1/23/2018 4:45 PM, Lee Daly wrote:
> > This updates the Intel and IBM license on files in examples to be the standard
> > BSD-3-Clause license used for the rest of DPDK,
> > bringing the files in compliance with the DPDK licensing policy.
> >
> > Signed-off-by: Lee Daly <lee.daly@intel.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Previous, non-split, version of the patch was acked:
Acked-by: Chao Zhu <chaozhu@linux.vnet.ibm.com>
see http://dpdk.org/ml/archives/dev/2018-February/090532.html
Applied, thanks
next prev parent reply other threads:[~2018-02-08 21:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 14:39 [dpdk-dev] [PATCH] examples: " Lee Daly
2018-01-22 12:48 ` Olivier Matz
2018-01-22 12:57 ` Hemant Agrawal
2018-01-23 16:43 ` [dpdk-dev] [PATCH] examples/cmdline: " Lee Daly
2018-02-07 16:15 ` Ferruh Yigit
2018-02-12 10:16 ` Olivier Matz
2018-02-13 22:25 ` Thomas Monjalon
2018-01-23 16:44 ` [dpdk-dev] [PATCH] examples/ip_pipeline: " Lee Daly
2018-01-23 17:08 ` Bruce Richardson
2018-01-24 13:20 ` Lee Daly
2018-01-26 9:24 ` Olivier Matz
2018-01-29 13:32 ` [dpdk-dev] [PATCH v2] " Lee Daly
2018-02-07 16:28 ` [dpdk-dev] [PATCH v3] " Lee Daly
2018-02-07 16:43 ` [dpdk-dev] [PATCH v4] " Lee Daly
2018-02-08 8:31 ` Hemant Agrawal
2018-02-12 10:15 ` Olivier Matz
2018-02-13 22:28 ` Thomas Monjalon
2018-01-24 13:27 ` [dpdk-dev] [PATCH] examples: update copyrights " Lee Daly
2018-02-07 16:15 ` Ferruh Yigit
2018-02-07 16:24 ` Jerin Jacob
2018-02-08 8:29 ` Hemant Agrawal
2018-02-08 14:03 ` [dpdk-dev] [PATCH v2] examples/performance-thread: " Lee Daly
2018-02-08 14:55 ` Ferruh Yigit
2018-02-08 21:36 ` Thomas Monjalon
2018-01-23 16:45 ` [dpdk-dev] [PATCH] examples/l3fwd: update copyright " Lee Daly
2018-02-07 16:15 ` Ferruh Yigit
2018-02-08 21:47 ` Thomas Monjalon [this message]
2018-01-23 16:45 ` [dpdk-dev] [PATCH] examples/l3fwd: update copyright and licenses Lee Daly
2018-02-07 16:15 ` Ferruh Yigit
2018-02-08 8:35 ` Hemant Agrawal
2018-02-08 8:39 ` Hemant Agrawal
2018-05-25 10:07 ` Thomas Monjalon
2018-01-23 16:46 ` [dpdk-dev] [PATCH] examples: update copyrights and license Lee Daly
2018-01-23 17:09 ` Bruce Richardson
2018-02-08 8:49 ` Hemant Agrawal
2018-02-08 13:48 ` Daly, Lee
2018-02-09 4:55 ` Hemant Agrawal
2018-02-09 14:30 ` Hasan Alayli
2018-02-09 15:09 ` Hemant Agrawal
2018-01-23 16:46 ` [dpdk-dev] [PATCH] examples: update copyrights and licenses Lee Daly
2018-02-08 7:58 ` [dpdk-dev] [PATCH] examples: update copyright and license Chao Zhu
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=2998814.o19V8NsUOD@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=chaozhu@linux.vnet.ibm.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=lee.daly@intel.com \
--cc=orika@mellanox.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=radu.nicolau@intel.com \
--cc=remy.horton@intel.com \
--cc=tomasz.kantecki@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).