From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, Jerin Jacob <jerin.jacob@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH] usertools: change to SPDX license identifier
Date: Wed, 11 Apr 2018 01:50:24 +0200 [thread overview]
Message-ID: <6832157.Y9ibbOLv6c@xps> (raw)
In-Reply-To: <20180409090757.GA18554@jerin>
09/04/2018 11:07, Jerin Jacob:
> -----Original Message-----
> > Date: Mon, 9 Apr 2018 14:28:37 +0530
> > From: Hemant Agrawal <hemant.agrawal@nxp.com>
> > To: dev@dpdk.org
> > CC: jerin.jacob@caviumnetworks.com, Hemant Agrawal <hemant.agrawal@nxp.com>
> > Subject: [PATCH] usertools: change to SPDX license identifier
> > X-Mailer: git-send-email 2.7.4
> >
> > Cc: jerin.jacob@caviumnetworks.com
> >
> > Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
>
> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Applied, thanks
next prev parent reply other threads:[~2018-04-10 23:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 8:58 [dpdk-dev] [PATCH] net/vmxnet3: change the SPDX tag style Hemant Agrawal
2018-04-09 8:58 ` [dpdk-dev] [PATCH] eal: add missing SPDX identifiers Hemant Agrawal
2018-05-25 8:20 ` Thomas Monjalon
2018-04-09 8:58 ` [dpdk-dev] [PATCH] test/crypto-perf: add missing SPDX identifier Hemant Agrawal
2018-04-17 15:08 ` De Lara Guarch, Pablo
2018-04-17 15:10 ` De Lara Guarch, Pablo
2018-04-09 8:58 ` [dpdk-dev] [PATCH] usertools: " Hemant Agrawal
2018-04-09 10:24 ` Neil Horman
2018-04-10 23:50 ` Thomas Monjalon
2018-04-09 8:58 ` [dpdk-dev] [PATCH] usertools: change to SPDX license identifier Hemant Agrawal
2018-04-09 9:07 ` Jerin Jacob
2018-04-10 23:50 ` Thomas Monjalon [this message]
2018-04-09 8:58 ` [dpdk-dev] [PATCH] kernel: add missing " Hemant Agrawal
2018-04-09 8:58 ` [dpdk-dev] [PATCH] pkg: change to " Hemant Agrawal
2018-05-25 8:22 ` Thomas Monjalon
2018-04-12 21:39 ` [dpdk-dev] [PATCH] net/vmxnet3: change the SPDX tag style Yong Wang
2018-04-17 17:44 ` Ferruh Yigit
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=6832157.Y9ibbOLv6c@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.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).