From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"colin.king@canonical.com" <colin.king@canonical.com>,
"christian.ehrhardt@canonical.com"
<christian.ehrhardt@canonical.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] doc: change tools guide to SPDX license
Date: Thu, 1 Aug 2019 07:15:01 +0000 [thread overview]
Message-ID: <VI1PR0401MB2541E6C3BCBACD696A6A76D089DE0@VI1PR0401MB2541.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <63eed503-c214-76a4-3683-00deb3ca5ce1@nxp.com>
Hi Thomas,
Please apply this patch.
Regards,
Hemant
On Wed, Jun 6, 2018 at 5:39 PM Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
>
> Christian,
> Will you please ack it? A ack from canonical is must to change the license (even if it is just the style).
Sorry Hemant for the extra delay, I was on PTO and this was lost in the mail flood afterwards.
Thanks Thomas & Colin for the extra pings to not get lost.
Acked-By: Christian Ehrhardt <christian.ehrhardt@canonical.com>
--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Hemant Agrawal
> Sent: Wednesday, September 26, 2018 9:17 PM
> To: dev@dpdk.org; colin.king@canonical.com;
> christian.ehrhardt@canonical.com
> Cc: thomas@monjalon.net; john.mcnamara@intel.com
> Subject: Re: [dpdk-dev] [PATCH] doc: change tools guide to SPDX license
>
> Colin/Christian,
>
> Can you or someone from canonical ack this patch.
>
> This is one of the last remaining roadblock in making DPDK SPDX complaint.
>
> Regards,
> Hemant
>
>
> On 7/4/2018 12:51 PM, Hemant Agrawal wrote:
> > Colin/Christian,
> >
> > Can someone from canonical ack this patch.
> >
> > Regards,
> > Hemant
> >
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Hemant Agrawal
> > Sent: Tuesday, June 5, 2018 1:20 PM
> > To: dev@dpdk.org
> > Cc: thomas@monjalon.net; john.mcnamara@intel.com;
> christian.ehrhardt@canonical.com
> > Subject: [dpdk-dev] [PATCH] doc: change tools guide to SPDX license
> >
> > Cc: christian.ehrhardt@canonical.com
> >
> > Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> > ---
> > doc/guides/tools/devbind.rst | 29 +----------------------------
> > doc/guides/tools/index.rst | 29 +----------------------------
> > doc/guides/tools/pmdinfo.rst | 28 +---------------------------
> > 3 files changed, 3 insertions(+), 83 deletions(-)
> >
> > diff --git a/doc/guides/tools/devbind.rst b/doc/guides/tools/devbind.rst
> index cabd99d..a2910e1 100644
> > --- a/doc/guides/tools/devbind.rst
> > +++ b/doc/guides/tools/devbind.rst
> > @@ -1,33 +1,6 @@
> > -.. BSD LICENSE
> > +.. SPDX-License-Identifier: BSD-3-Clause
> > Copyright(c) 2016 Canonical Limited. 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.
> > -
> > -
> > dpdk-devbind Application
> > ========================
> >
> > diff --git a/doc/guides/tools/index.rst b/doc/guides/tools/index.rst index
> a6e2c4c..d63e191 100644
> > --- a/doc/guides/tools/index.rst
> > +++ b/doc/guides/tools/index.rst
> > @@ -1,32 +1,5 @@
> > -.. BSD LICENSE
> > +.. SPDX-License-Identifier: BSD-3-Clause
> > Copyright(c) 2016 Canonical Limited. 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.
> >
> > DPDK Tools User Guides
> > ======================
> > diff --git a/doc/guides/tools/pmdinfo.rst b/doc/guides/tools/pmdinfo.rst
> index efbf527..af6d24b 100644
> > --- a/doc/guides/tools/pmdinfo.rst
> > +++ b/doc/guides/tools/pmdinfo.rst
> > @@ -1,32 +1,6 @@
> > -.. BSD LICENSE
> > +.. SPDX-License-Identifier: BSD-3-Clause
> > Copyright(c) 2016 Canonical Limited. 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.
> > -
> >
> > dpdk-pmdinfo Application
> > ========================
> > --
> > 2.7.4
> >
next prev parent reply other threads:[~2019-08-01 7:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 7:50 Hemant Agrawal
2018-06-05 7:50 ` [dpdk-dev] [PATCH] doc: add SPDX and copyright to rel notes Hemant Agrawal
2018-07-26 20:44 ` Thomas Monjalon
2018-07-27 4:54 ` [dpdk-dev] [PATCH v2] " Hemant Agrawal
2018-08-09 20:36 ` Thomas Monjalon
2018-06-05 7:50 ` [dpdk-dev] [PATCH] doc: add SPDX and copyright to contributing guide Hemant Agrawal
2018-08-09 20:45 ` Thomas Monjalon
2018-06-05 7:50 ` [dpdk-dev] [PATCH] buildtools: change license to SPDX Hemant Agrawal
2018-06-05 11:27 ` Neil Horman
2018-07-26 20:45 ` Thomas Monjalon
2018-07-04 7:21 ` [dpdk-dev] [PATCH] doc: change tools guide to SPDX license Hemant Agrawal
2018-09-26 15:47 ` Hemant Agrawal
2019-08-01 7:15 ` Hemant Agrawal [this message]
2019-08-05 14:17 ` Thomas Monjalon
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=VI1PR0401MB2541E6C3BCBACD696A6A76D089DE0@VI1PR0401MB2541.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=christian.ehrhardt@canonical.com \
--cc=colin.king@canonical.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).