mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Diaz <didou.diaz@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Possible dual license for rbtree ?
Date: Mon, 3 Apr 2023 11:21:39 +0200	[thread overview]
Message-ID: <180269da-a7a3-97be-4e8e-c8b82e33d430@gmail.com> (raw)

Dear Linux maintainers,

This is a question about a possible dual license for the rbtree 
implementation (lib/rbtree.c).
Please apologize if it is not the right place to ask.
Thank you for personally CC me in the answers/comments posted to the 
list in response to this post.

Looking for an efficient red-black tree implementation in C, I 
discovered the wonderful rbtree utility. I really appreciate the clever 
approach of this « invasive » implementation on the top of which one can 
build his specific maps. I saw this rbtree implementation is famous and 
widely mentioned but its usage is limited by its GPL license.

Could you consider extending this license by a dual license as allowed 
by docs.kernel.org/process/license-rules.html which states the some 
individual files can be provided under a dual license including MIT, 
BSD, etc.

Would then it be possible to release rbtree under a dual license more 
permissive, e.g. MIT ?
Be sure this would be very appreciated by a lot of C programmers !

This comes down to modyfy the SPDX descriptions of lib/rbtree.c and 
include/rbtree.h, include/rbtree_augmented.h, include/rbtree_types.h as 
follows:

     SPDX-License-Identifier: GPL-2.0-or-later OR MIT

Thank you for your attention.

Daniel



             reply	other threads:[~2023-04-03  9:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03  9:21 Daniel Diaz [this message]
2023-04-16 11:28 ` Daniel Diaz

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=180269da-a7a3-97be-4e8e-c8b82e33d430@gmail.com \
    --to=didou.diaz@gmail.com \
    --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

all inboxes | Powered by JetHome®