From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Ethan Zhuang <zhuangwj@gmail.com>
Subject: Re: [dpdk-dev] [PATCH 4/7] kni: add SPDX license tag
Date: Thu, 28 Nov 2019 02:31:56 +0100 [thread overview]
Message-ID: <2140607.atfi6UnY3l@xps> (raw)
In-Reply-To: <VI1PR0401MB25412DEF40AC14CFA0AA8F6489860@VI1PR0401MB2541.eurprd04.prod.outlook.com>
26/09/2019 09:39, Hemant Agrawal:
> ++ Ethan Zhuang <zhuangwj@gmail.com>.
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Already acked (and merged) from another series.
next prev parent reply other threads:[~2019-11-28 1:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 15:51 [dpdk-dev] [PATCH 0/7] SPDX license tag changes Stephen Hemminger
2019-09-25 15:51 ` [dpdk-dev] [PATCH 1/7] uuid: remove BSD boilerplate Stephen Hemminger
2019-09-26 6:52 ` Hemant Agrawal
2019-11-28 1:44 ` Thomas Monjalon
2019-09-25 15:51 ` [dpdk-dev] [PATCH 2/7] reciprocal: remove redundant boilerplate Stephen Hemminger
2019-11-28 1:49 ` Thomas Monjalon
2019-09-25 15:51 ` [dpdk-dev] [PATCH 3/7] windows: remove boilerplate from BSD header Stephen Hemminger
2019-09-26 7:38 ` Hemant Agrawal
2019-09-25 15:51 ` [dpdk-dev] [PATCH 4/7] kni: add SPDX license tag Stephen Hemminger
2019-09-26 7:39 ` Hemant Agrawal
2019-11-28 1:31 ` Thomas Monjalon [this message]
2019-09-25 15:51 ` [dpdk-dev] [PATCH 5/7] ethdev: add SPDX tags to pci and vdev headers Stephen Hemminger
2019-09-26 7:39 ` Hemant Agrawal
2019-09-25 15:51 ` [dpdk-dev] [PATCH 6/7] testpmd: add SPDX license tags Stephen Hemminger
2019-09-26 7:40 ` Hemant Agrawal
2019-09-25 15:51 ` [dpdk-dev] [PATCH 7/7] test: add SPDX headers Stephen Hemminger
2019-09-26 7:40 ` Hemant Agrawal
2019-10-04 10:23 ` Vladimir Medvedkin
2019-12-02 14:05 ` Trahe, Fiona
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=2140607.atfi6UnY3l@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=stephen@networkplumber.org \
--cc=zhuangwj@gmail.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).