From: Alejandro Lucero <alejandro.lucero@netronome.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: replace license text with SPDX tag for NFP nic
Date: Wed, 6 Nov 2019 13:19:53 +0000 [thread overview]
Message-ID: <CAD+H9915FMOpfUWAYCZRAt5KiHBAgUf_CHYkXLV8rGbcZrGn_Q@mail.gmail.com> (raw)
In-Reply-To: <20190927090433.32311-6-hemant.agrawal@nxp.com>
On Fri, Sep 27, 2019 at 10:06 AM Hemant Agrawal <hemant.agrawal@nxp.com>
wrote:
> Cc: Alejandro Lucero <alejandro.lucero@netronome.com>
>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
> doc/guides/nics/nfp.rst | 28 +---------------------------
> 1 file changed, 1 insertion(+), 27 deletions(-)
>
> diff --git a/doc/guides/nics/nfp.rst b/doc/guides/nics/nfp.rst
> index 309fa5d39..5f2a0698f 100644
> --- a/doc/guides/nics/nfp.rst
> +++ b/doc/guides/nics/nfp.rst
> @@ -1,33 +1,7 @@
> -.. BSD LICENSE
> +.. SPDX-License-Identifier: BSD-3-Clause
> Copyright(c) 2015-2017 Netronome Systems, Inc. All rights reserved.
> All rights reserved.
>
> - Redistribution and use in source and binary forms, with or without
> - modification, are permitted provided that the following conditions
> - are met:
> -
> - * Redistributions of source code must retain the above copyright
> - notice, this list of conditions and the following disclaimer.
> - * Redistributions in binary form must reproduce the above copyright
> - notice, this list of conditions and the following disclaimer in
> - the documentation and/or other materials provided with the
> - distribution.
> - * Neither the name of Intel Corporation nor the names of its
> - contributors may be used to endorse or promote products derived
> - from this software without specific prior written permission.
> -
> - THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
> - "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
> - LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
> - A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
> - OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
> - SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
> - LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
> - DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
> - THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> - (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
> - OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> -
> NFP poll mode driver library
> ============================
>
> --
> 2.17.1
>
>
Acked-by: Alejandro Lucero <alejandro.lucero@netronome.com>
next prev parent reply other threads:[~2019-11-06 13:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 9:04 [dpdk-dev] [PATCH] eal/ppc_64: add SPDX license tag Hemant Agrawal
2019-09-27 9:04 ` [dpdk-dev] [PATCH] net/sfc: add SPDX tag in meson build Hemant Agrawal
2019-11-07 9:12 ` [dpdk-dev] FW: " Hemant Agrawal
2019-11-07 10:54 ` [dpdk-dev] " Andrew Rybchenko
2019-11-07 15:32 ` Ferruh Yigit
2019-09-27 9:04 ` [dpdk-dev] [PATCH] examples/netmap_compat: replace license text with SPDX tag Hemant Agrawal
2019-09-27 9:04 ` [dpdk-dev] [PATCH] doc: replace license text with SPDX tag in ARK nic Hemant Agrawal
2019-10-11 13:10 ` Ed Czeck
2019-10-14 9:26 ` Ferruh Yigit
2019-09-27 9:04 ` [dpdk-dev] [PATCH] doc: replace license text with SPDX tag for AVP nic Hemant Agrawal
2019-09-27 11:00 ` Legacy, Allain
2019-10-14 9:27 ` Ferruh Yigit
2019-09-27 9:04 ` [dpdk-dev] [PATCH] doc: replace license text with SPDX tag for NFP nic Hemant Agrawal
2019-11-06 13:19 ` Alejandro Lucero [this message]
2019-11-06 14:04 ` Ferruh Yigit
2019-09-27 23:45 ` [dpdk-dev] [PATCH] eal/ppc_64: add SPDX license tag David Christensen
2019-10-17 5:01 ` David Marchand
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=CAD+H9915FMOpfUWAYCZRAt5KiHBAgUf_CHYkXLV8rGbcZrGn_Q@mail.gmail.com \
--to=alejandro.lucero@netronome.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.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).