From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
Coly Li <colyli@suse.de>,
Ciaran Farrell <ciaran.farrell@suse.com>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
linux-bcache@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Philippe Ombredanne <pombredanne@nexb.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Jonas Oberg <jonas@fsfe.org>
Subject: Re: PostgreSQL licensed code on Linux
Date: Tue, 29 May 2018 16:51:44 -0400 [thread overview]
Message-ID: <20180529205143.GB7381@thunk.org> (raw)
In-Reply-To: <20180529192643.GA3487@kmo-pixel>
On Tue, May 29, 2018 at 03:26:43PM -0400, Kent Overstreet wrote:
> > That seems to indicate that we've had already PostgreSQL licensed code on
> > Linux since Kent's addition of bcache to Linux in 2013. The portion of code
> > is rather small though, to me it seems to cover only crc_table[],
> > bch_crc64_update(), and bch_crc64().
>
> > As silly as it may be we should split out the PostgreSQL licensed code from
> > drivers/md/bcache/util.c into its own file and while at it clarify the
> > license.
While we're at it maybe we should move the crc-64 code to lib and/or
crypto, alongside our support for crc-8, crc-16, and crc-32
algorithms? That way if there are other potential users for crc-64,
they will be less likely to re-invent the wheel....
- Ted
next prev parent reply other threads:[~2018-05-29 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 19:14 PostgreSQL licensed code on Linux Luis R. Rodriguez
2018-05-29 19:26 ` Kent Overstreet
2018-05-29 20:51 ` Theodore Y. Ts'o [this message]
2018-05-29 21:00 ` Kent Overstreet
2018-05-29 22:59 ` Luis R. Rodriguez
2018-05-29 23:12 ` Luis R. Rodriguez
2018-05-29 23:22 ` Andy Shevchenko
2018-05-30 0:03 ` Luis R. Rodriguez
2018-05-30 0:10 ` Andy Shevchenko
2018-05-29 22:55 ` Luis R. Rodriguez
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=20180529205143.GB7381@thunk.org \
--to=tytso@mit.edu \
--cc=ciaran.farrell@suse.com \
--cc=colyli@suse.de \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jonas@fsfe.org \
--cc=kent.overstreet@gmail.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=pombredanne@nexb.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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