From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: keyrings@vger.kernel.org
Cc: David Howells <dhowells@redhat.com>,
AndrewMorton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH] lib: update the licence of the ASN.1 encoder and decoder
Date: Thu, 16 Oct 2025 14:24:40 -0400 [thread overview]
Message-ID: <b419422e5e8f280e698c62461d04ccf6c8ba060f.camel@HansenPartnership.com> (raw)
The open source project leancrypto (github.com/smuellerDD/leancrypto)
has asked to use the ASN.1 encoder/decoder files from the kernel.
Since leancrypto is licensed under BSD-3-Clause the fairest thing to do
for everyone is add BSD-3-Clause as an OR to the SPDX tag so every
project could import them under the same terms.
The copyright holders of both files have agreed to this change.
Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
---
lib/asn1_decoder.c | 2 +-
lib/asn1_encoder.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/asn1_decoder.c b/lib/asn1_decoder.c
index 5738ae286b41..1be81a80aed7 100644
--- a/lib/asn1_decoder.c
+++ b/lib/asn1_decoder.c
@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: GPL-2.0-or-later
+// SPDX-License-Identifier: GPL-2.0-or-later OR BSD-3-Clause
/* Decoder for ASN.1 BER/DER/CER encoded bytestream
*
* Copyright (C) 2012 Red Hat, Inc. All Rights Reserved.
diff --git a/lib/asn1_encoder.c b/lib/asn1_encoder.c
index 92f35aae13b1..e1285208478d 100644
--- a/lib/asn1_encoder.c
+++ b/lib/asn1_encoder.c
@@ -1,4 +1,4 @@
-// SPDX-License-Identifier: GPL-2.0-only
+// SPDX-License-Identifier: GPL-2.0-only OR BSD-3-Clause
/*
* Simple encoder primitives for ASN.1 BER/DER/CER
*
--
2.51.0
reply other threads:[~2025-10-16 18:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b419422e5e8f280e698c62461d04ccf6c8ba060f.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).