From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Franziska Naepelt <franziska.naepelt@googlemail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux SPDX Licenses <linux-spdx@vger.kernel.org>,
Linux Kernel Janitors <kernel-janitors@vger.kernel.org>,
Linux Crypto <linux-crypto@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Alexey Degtyarev <alexey@renatasystems.org>,
Vitaly Chikunov <vt@altlinux.org>
Subject: [PATCH 5/8] crypto: streebog_generic: Correct SPDX license identifier
Date: Wed, 7 Jun 2023 12:39:46 +0700 [thread overview]
Message-ID: <20230607053940.39078-15-bagasdotme@gmail.com> (raw)
In-Reply-To: <20230607053940.39078-10-bagasdotme@gmail.com>
Streebog hash function implementation (crypto/streebog_generic.c) have
GPL 2.0+ license boilerplate, but its SPDX identifier is mistagged
as dual BSD/GPL. Correct the tag, while also removing the boilerplate.
Fixes: e18957e8e87403 ("crypto: streebog - add Streebog hash function")
Cc: Alexey Degtyarev <alexey@renatasystems.org>
Cc: Vitaly Chikunov <vt@altlinux.org>
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
crypto/streebog_generic.c | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/crypto/streebog_generic.c b/crypto/streebog_generic.c
index dc625ffc54ad7f..65d0e6bf5e1992 100644
--- a/crypto/streebog_generic.c
+++ b/crypto/streebog_generic.c
@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: GPL-2.0+ OR BSD-2-Clause
+// SPDX-License-Identifier: GPL-2.0-or-later
/*
* Streebog hash function as specified by GOST R 34.11-2012 and
* described at https://tools.ietf.org/html/rfc6986
@@ -6,10 +6,6 @@
* Copyright (c) 2013 Alexey Degtyarev <alexey@renatasystems.org>
* Copyright (c) 2018 Vitaly Chikunov <vt@altlinux.org>
*
- * 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.
*/
#include <crypto/internal/hash.h>
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-06-07 5:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 5:39 [PATCH 0/8] SPDX conversion for cryptographic algorithms Bagas Sanjaya
2023-06-07 5:39 ` [PATCH 1/8] crypto: Convert dual BSD 3-Clause/GPL 2.0 boilerplate to SPDX identifier Bagas Sanjaya
2023-06-07 14:10 ` Richard Fontana
2023-06-08 5:56 ` Bagas Sanjaya
2023-06-08 8:37 ` Ard Biesheuvel
2023-06-08 9:05 ` Greg Kroah-Hartman
2023-06-08 9:07 ` Ard Biesheuvel
2023-06-07 5:39 ` [PATCH 2/8] crypto: fcrypt: Replace dual BSD 3-Clause/GPL 2.0+ boilerplate with " Bagas Sanjaya
2023-06-07 5:39 ` [PATCH 3/8] crypto: drbg: Convert dual BSD 3-Clause/GPL-1.0 license boilerplate to " Bagas Sanjaya
2023-06-07 13:56 ` Richard Fontana
2023-06-08 5:45 ` Bagas Sanjaya
2023-06-07 5:39 ` [PATCH 4/8] crypto: ecc: Replace BSD 2-Clause license boilerplate with " Bagas Sanjaya
2023-06-07 5:39 ` Bagas Sanjaya [this message]
2023-06-07 5:39 ` [PATCH 6/8] crypto: Replace GPL 2.0 boilerplate with SPDX license identifier Bagas Sanjaya
2023-06-07 5:39 ` [PATCH 7/8] crypto: ecrdsa: Remove GPL 2.0+ boilerplate Bagas Sanjaya
2023-06-07 5:39 ` [PATCH 8/8] crypto: cts: Convert MIT boilerplate to corresponding SPDX license identifier Bagas Sanjaya
2023-06-07 13:47 ` Richard Fontana
2023-06-08 5:32 ` Bagas Sanjaya
2023-06-08 5:40 ` Greg Kroah-Hartman
2023-06-08 6:49 ` Bagas Sanjaya
2023-06-08 6:54 ` Greg Kroah-Hartman
2023-06-08 11:12 ` Dan Carpenter
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=20230607053940.39078-15-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=alexey@renatasystems.org \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=franziska.naepelt@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=vt@altlinux.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