From: "Chris Mason" <clm@fb.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: <linux-fscrypt@vger.kernel.org>, Jes Sorensen <jsorensen@fb.com>,
Jes Sorensen <jes.sorensen@gmail.com>, <kernel-team@fb.com>,
Victor Hsieh <victorhsieh@google.com>
Subject: Re: [fsverity-utils PATCH] Switch to MIT license
Date: Fri, 31 Jul 2020 16:31:32 -0400 [thread overview]
Message-ID: <97CF68DA-3272-41D8-ACB2-544704C343BF@fb.com> (raw)
In-Reply-To: <20200731191156.22602-1-ebiggers@kernel.org>
On 31 Jul 2020, at 15:11, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> This allows libfsverity to be used by software with other common
> licenses, e.g. LGPL, MIT, BSD, and Apache 2.0. It also avoids the
> incompatibility that some people perceive between OpenSSL and the GPL.
>
> See discussion at
> https://lkml.kernel.org/linux-fscrypt/20200211000037.189180-1-Jes.Sorensen@gmail.com/T/#u
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Acked-by: Chris Mason <clm@fb.com> # FB copyrighted material
next prev parent reply other threads:[~2020-07-31 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 19:11 [fsverity-utils PATCH] Switch to MIT license Eric Biggers
2020-07-31 20:31 ` Chris Mason [this message]
2020-07-31 20:37 ` Jes Sorensen
2020-08-01 17:57 ` Eric Biggers
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=97CF68DA-3272-41D8-ACB2-544704C343BF@fb.com \
--to=clm@fb.com \
--cc=ebiggers@kernel.org \
--cc=jes.sorensen@gmail.com \
--cc=jsorensen@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-fscrypt@vger.kernel.org \
--cc=victorhsieh@google.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;
as well as URLs for NNTP newsgroup(s).