All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH] tinycompress: clarify dual-license wording
Date: Fri, 20 Oct 2017 11:28:31 +0530	[thread overview]
Message-ID: <20171020055831.GK30097@localhost> (raw)
In-Reply-To: <20171018181125.27538-1-pierre-louis.bossart@linux.intel.com>

On Wed, Oct 18, 2017 at 01:11:25PM -0500, Pierre-Louis Bossart wrote:
> There were reports of confusion in legal circles introduced by the wording
> "tinycompress is provided under LGPL and BSD dual license" in the README.
> 
> Clarify with the addition of the wording traditionally used for dual licenses:
> 
> "This file is provided under a dual BSD/LGPLv2.1 license.  When using or
> redistributing this file, you may do so under either license"

Applied, thanks

-- 
~Vinod

      reply	other threads:[~2017-10-20  5:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18 18:11 [PATCH] tinycompress: clarify dual-license wording Pierre-Louis Bossart
2017-10-20  5:58 ` Vinod Koul [this message]

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=20171020055831.GK30097@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.