From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] net/sfc: change license to BSD-3-Clause
Date: Tue, 9 Jan 2018 13:33:32 +0530 [thread overview]
Message-ID: <7ba4e244-91c4-1a70-d6e6-9e05f529838c@nxp.com> (raw)
In-Reply-To: <1515418535-16575-2-git-send-email-arybchenko@solarflare.com>
On 1/8/2018 7:05 PM, Andrew Rybchenko wrote:
> Change license from BSD-2-Clause to BSD-3-Clause.
> Bump copyright year.
>
> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
> ---
> drivers/net/sfc/Makefile | 26 ++------------------------
> drivers/net/sfc/efsys.h | 26 ++------------------------
> drivers/net/sfc/sfc.c | 26 ++------------------------
> drivers/net/sfc/sfc.h | 26 ++------------------------
> drivers/net/sfc/sfc_debug.h | 26 ++------------------------
> drivers/net/sfc/sfc_dp.c | 26 ++------------------------
> drivers/net/sfc/sfc_dp.h | 26 ++------------------------
> drivers/net/sfc/sfc_dp_rx.h | 26 ++------------------------
> drivers/net/sfc/sfc_dp_tx.h | 26 ++------------------------
> drivers/net/sfc/sfc_ef10.h | 26 ++------------------------
> drivers/net/sfc/sfc_ef10_rx.c | 26 ++------------------------
> drivers/net/sfc/sfc_ef10_tx.c | 26 ++------------------------
> drivers/net/sfc/sfc_ethdev.c | 26 ++------------------------
> drivers/net/sfc/sfc_ev.c | 26 ++------------------------
> drivers/net/sfc/sfc_ev.h | 26 ++------------------------
> drivers/net/sfc/sfc_filter.c | 26 ++------------------------
> drivers/net/sfc/sfc_filter.h | 26 ++------------------------
> drivers/net/sfc/sfc_flow.c | 26 ++------------------------
> drivers/net/sfc/sfc_flow.h | 26 ++------------------------
> drivers/net/sfc/sfc_intr.c | 26 ++------------------------
> drivers/net/sfc/sfc_kvargs.c | 26 ++------------------------
> drivers/net/sfc/sfc_kvargs.h | 26 ++------------------------
> drivers/net/sfc/sfc_log.h | 26 ++------------------------
> drivers/net/sfc/sfc_mcdi.c | 26 ++------------------------
> drivers/net/sfc/sfc_port.c | 26 ++------------------------
> drivers/net/sfc/sfc_rx.c | 26 ++------------------------
> drivers/net/sfc/sfc_rx.h | 26 ++------------------------
> drivers/net/sfc/sfc_tso.c | 26 ++------------------------
> drivers/net/sfc/sfc_tweak.h | 26 ++------------------------
> drivers/net/sfc/sfc_tx.c | 26 ++------------------------
> drivers/net/sfc/sfc_tx.h | 26 ++------------------------
> 31 files changed, 62 insertions(+), 744 deletions(-)
>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
<snip..>
next prev parent reply other threads:[~2018-01-09 8:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-08 13:35 [dpdk-dev] [PATCH 1/2] net/sfc/base: " Andrew Rybchenko
2018-01-08 13:35 ` [dpdk-dev] [PATCH 2/2] net/sfc: " Andrew Rybchenko
2018-01-09 8:03 ` Hemant Agrawal [this message]
2018-01-09 8:04 ` [dpdk-dev] [PATCH 1/2] net/sfc/base: " Hemant Agrawal
2018-01-09 19:38 ` Ferruh Yigit
2018-01-09 19:59 ` Andrew Rybchenko
2018-01-10 10:23 ` Bruce Richardson
2018-01-10 10:38 ` Hemant Agrawal
2018-01-10 19:42 ` 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=7ba4e244-91c4-1a70-d6e6-9e05f529838c@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
/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).