From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Franziska Naepelt <franziska.naepelt@googlemail.com>
Cc: davem@davemloft.net, franziska.naepelt@gmail.com,
herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, martin.petersen@oracle.com,
tim.c.chen@linux.intel.com
Subject: Re: [PATCH v2] crypto: crct10dif_common Add SPDX-License-Identifier tag
Date: Wed, 7 Jun 2023 12:59:08 +0700 [thread overview]
Message-ID: <ZIAcrKAsBZk8mYOg@debian.me> (raw)
In-Reply-To: <ZH_-c_WHg2jz0W1R@debian.me>
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
On Wed, Jun 07, 2023 at 10:50:11AM +0700, Bagas Sanjaya wrote:
> On Tue, Jun 06, 2023 at 08:07:13PM +0200, Franziska Naepelt wrote:
> > +// SPDX-License-Identifier: GPL-2.0-or-later
> > /*
> > * Cryptographic API.
> > *
> > @@ -7,21 +8,6 @@
> > * Written by Martin K. Petersen <martin.petersen@oracle.com>
> > * Copyright (C) 2013 Intel Corporation
> > * Author: Tim Chen <tim.c.chen@linux.intel.com>
> > - *
> > - * This program is free software; you can redistribute it and/or modify it
> > - * under the terms of the GNU General Public License as published by the Free
> > - * Software Foundation; either version 2 of the License, or (at your option)
> > - * any later version.
> > - *
> > - * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
> > - * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
> > - * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
> > - * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
> > - * BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
> > - * ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
> > - * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
> > - * SOFTWARE.
> > - *
> > */
>
> LGTM but I'll send a SPDX conversion series for crypto/ instead soon.
>
OK, here's the series [1].
[1]: https://lore.kernel.org/lkml/20230607053940.39078-10-bagasdotme@gmail.com/
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-06-07 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 11:03 [PATCH] crypto: crct10dif_common Add SPDX-License-Identifier tag Franziska Naepelt
2023-06-06 12:33 ` Bagas Sanjaya
2023-06-06 18:07 ` [PATCH v2] " Franziska Naepelt
2023-06-07 3:50 ` Bagas Sanjaya
2023-06-07 5:59 ` Bagas Sanjaya [this message]
2023-06-16 12:17 ` Herbert Xu
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=ZIAcrKAsBZk8mYOg@debian.me \
--to=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=franziska.naepelt@gmail.com \
--cc=franziska.naepelt@googlemail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tim.c.chen@linux.intel.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