DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Lee Daly <lee.daly@intel.com>
Cc: dev@dpdk.org, Olivier Matz <olivier.matz@6wind.com>,
	cristian.dumitrescu@intel.com, ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH v4] examples/ip_pipeline: update copyright and license
Date: Tue, 13 Feb 2018 23:28:39 +0100	[thread overview]
Message-ID: <2692062.Ivrz1UTxaV@xps> (raw)
In-Reply-To: <20180212101542.dzmttxmz2np4w4jk@platinum>

12/02/2018 11:15, Olivier Matz:
> On Wed, Feb 07, 2018 at 04:43:59PM +0000, Lee Daly wrote:
> > This updates the Intel and Oliver Matz licenses on a file 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>
> 
> Acked-by: Olivier Matz <olivier.matz@6wind.com>

Applied, thanks

  reply	other threads:[~2018-02-13 22:28 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 [this message]
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
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=2692062.Ivrz1UTxaV@xps \
    --to=thomas@monjalon.net \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=lee.daly@intel.com \
    --cc=olivier.matz@6wind.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).