Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Daniel Axtens <dja@axtens.net>,
	linuxppc-dev@lists.ozlabs.org, linux-crypto@vger.kernel.org
Cc: anton@samba.org, Daniel Axtens <dja@axtens.net>
Subject: Re: [PATCH 2/4] crypto: powerpc - Re-enable non-REFLECTed CRCs
Date: Thu, 16 Mar 2017 21:44:03 +1100	[thread overview]
Message-ID: <871stxlcwc.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20170315123737.20234-2-dja@axtens.net>

Daniel Axtens <dja@axtens.net> writes:

> When CRC32c was included in the kernel, Anton ripped out
> the #ifdefs around reflected polynomials, because CRC32c
> is always reflected. However, not all CRCs use reflection
> so we'd like to make it optional.
>
> Restore the REFLECT parts from Anton's original CRC32
> implementation (https://github.com/antonblanchard/crc32-vpmsum)
>
> That implementation is available under GPLv2+, so we're OK
> from a licensing point of view:
> https://github.com/antonblanchard/crc32-vpmsum/blob/master/LICENSE.TXT

It's also written by Anton and copyright IBM, so you (we (IBM)) could
always just relicense it anyway.

So doubly OK IMO.

cheers

  reply	other threads:[~2017-03-16 10:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15 12:37 [PATCH 1/4] crypto: powerpc - Factor out the core CRC vpmsum algorithm Daniel Axtens
2017-03-15 12:37 ` [PATCH 2/4] crypto: powerpc - Re-enable non-REFLECTed CRCs Daniel Axtens
2017-03-16 10:44   ` Michael Ellerman [this message]
2017-03-15 12:37 ` [PATCH 3/4] crypto: powerpc - Add CRC-T10DIF acceleration Daniel Axtens
2017-03-15 12:37 ` [PATCH 4/4] crypto: powerpc - Stress test for vpmsum implementations Daniel Axtens
2017-03-15 16:10 ` [PATCH 1/4] crypto: powerpc - Factor out the core CRC vpmsum algorithm David Laight
2017-03-15 22:30   ` Daniel Axtens
2017-03-16  9:50     ` David Laight
2017-03-16 11:13   ` Anton Blanchard
2017-03-16 10:45 ` Michael Ellerman
2017-03-16 12:54   ` Daniel Axtens
2017-03-24 14:12 ` Herbert Xu

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=871stxlcwc.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=anton@samba.org \
    --cc=dja@axtens.net \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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