From: Sami Tolvanen <samitolvanen@google.com> To: Ard Biesheuvel <ard.biesheuvel@linaro.org> Cc: Andy Polyakov <appro@openssl.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>, Herbert Xu <herbert@gondor.apana.org.au>, "David S. Miller" <davem@davemloft.net> Subject: Re: [PATCH] arm: crypto: Add NEON optimized SHA-256 Date: Mon, 16 Mar 2015 16:23:04 +0000 [thread overview] Message-ID: <20150316162304.GA35408@google.com> (raw) In-Reply-To: <CAKv+Gu8+oQ13j61X6x70baJXOpEiM2L+vK=KgK1JG12sy5KMsg@mail.gmail.com> On Mon, Mar 16, 2015 at 05:08:03PM +0100, Ard Biesheuvel wrote: > Have you tested this code with the tcrypt.ko module? I have not, but I can look into it. > Did you talk to Andy about the license? I don't think this is > permissible for the kernel as-is. Unless I have misunderstood something, the license at the Cryptogams website includes an option to license the code under the GNU GPL. However, I can certainly contact Andy to clarify his intentions. > This is broken on thumb-2, use adr instead > You can also implement SHA-224 using the same core transform, it's > just some trivial glue code. > Could you please rebase this onto Herbert's cryptodev tree and move > this to arch/arm/crypto/Kconfig? Thanks for the comments, I will submit a second version once we have a clarification on the license. Sami
WARNING: multiple messages have this Message-ID (diff)
From: samitolvanen@google.com (Sami Tolvanen) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] arm: crypto: Add NEON optimized SHA-256 Date: Mon, 16 Mar 2015 16:23:04 +0000 [thread overview] Message-ID: <20150316162304.GA35408@google.com> (raw) In-Reply-To: <CAKv+Gu8+oQ13j61X6x70baJXOpEiM2L+vK=KgK1JG12sy5KMsg@mail.gmail.com> On Mon, Mar 16, 2015 at 05:08:03PM +0100, Ard Biesheuvel wrote: > Have you tested this code with the tcrypt.ko module? I have not, but I can look into it. > Did you talk to Andy about the license? I don't think this is > permissible for the kernel as-is. Unless I have misunderstood something, the license at the Cryptogams website includes an option to license the code under the GNU GPL. However, I can certainly contact Andy to clarify his intentions. > This is broken on thumb-2, use adr instead > You can also implement SHA-224 using the same core transform, it's > just some trivial glue code. > Could you please rebase this onto Herbert's cryptodev tree and move > this to arch/arm/crypto/Kconfig? Thanks for the comments, I will submit a second version once we have a clarification on the license. Sami
next prev parent reply other threads:[~2015-03-16 16:23 UTC|newest] Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-16 15:48 [PATCH] arm: crypto: Add NEON optimized SHA-256 Sami Tolvanen 2015-03-16 15:48 ` Sami Tolvanen 2015-03-16 16:08 ` Ard Biesheuvel 2015-03-16 16:08 ` Ard Biesheuvel 2015-03-16 16:23 ` Sami Tolvanen [this message] 2015-03-16 16:23 ` Sami Tolvanen 2015-03-17 6:56 ` Ard Biesheuvel 2015-03-17 6:56 ` Ard Biesheuvel 2015-03-17 15:09 ` Andy Polyakov 2015-03-17 15:09 ` Andy Polyakov 2015-03-17 15:21 ` Sami Tolvanen 2015-03-17 15:21 ` Sami Tolvanen 2015-03-17 15:51 ` Ard Biesheuvel 2015-03-17 15:51 ` Ard Biesheuvel 2015-03-23 13:50 ` [PATCHv2] arm: crypto: Add optimized SHA-256/224 Sami Tolvanen 2015-03-23 13:50 ` Sami Tolvanen 2015-03-23 18:26 ` Ard Biesheuvel 2015-03-23 18:26 ` Ard Biesheuvel 2015-03-24 11:35 ` Herbert Xu 2015-03-24 11:35 ` Herbert Xu 2015-03-24 11:40 ` Ard Biesheuvel 2015-03-24 11:40 ` Ard Biesheuvel 2015-03-24 11:46 ` Herbert Xu 2015-03-24 11:46 ` Herbert Xu 2015-03-24 11:57 ` Ard Biesheuvel 2015-03-24 11:57 ` Ard Biesheuvel 2015-03-24 11:32 ` Herbert Xu 2015-03-24 11:32 ` Herbert Xu 2015-03-24 11:33 ` Ard Biesheuvel 2015-03-24 11:33 ` Ard Biesheuvel 2015-03-24 12:27 ` Jean-Christophe PLAGNIOL-VILLARD 2015-03-24 12:27 ` Jean-Christophe PLAGNIOL-VILLARD 2015-03-24 12:42 ` Ard Biesheuvel 2015-03-24 12:42 ` Ard Biesheuvel 2015-03-24 13:05 ` Jean-Christophe PLAGNIOL-VILLARD 2015-03-24 13:05 ` Jean-Christophe PLAGNIOL-VILLARD 2015-03-24 13:06 ` Ard Biesheuvel 2015-03-24 13:06 ` Ard Biesheuvel 2015-03-24 14:46 ` Ard Biesheuvel 2015-03-24 14:46 ` Ard Biesheuvel 2015-03-24 17:05 ` Jean-Christophe PLAGNIOL-VILLARD 2015-03-24 17:05 ` Jean-Christophe PLAGNIOL-VILLARD 2015-03-24 17:40 ` Ard Biesheuvel 2015-03-24 17:40 ` Ard Biesheuvel 2015-03-24 18:17 ` Sami Tolvanen 2015-03-24 18:17 ` Sami Tolvanen 2015-03-25 6:49 ` Ard Biesheuvel 2015-03-25 6:49 ` Ard Biesheuvel 2015-03-27 10:42 ` Andy Polyakov 2015-03-27 10:42 ` Andy Polyakov 2015-03-27 10:44 ` Ard Biesheuvel 2015-03-27 10:44 ` Ard Biesheuvel 2015-03-27 18:07 ` Ard Biesheuvel 2015-03-27 18:07 ` Ard Biesheuvel 2015-03-29 13:27 ` Andy Polyakov 2015-03-29 13:27 ` Andy Polyakov 2015-03-30 8:37 ` [PATCHv3] " Sami Tolvanen 2015-03-30 8:37 ` Sami Tolvanen 2015-04-01 12:43 ` Herbert Xu 2015-04-01 12:43 ` Herbert Xu 2015-04-01 13:19 ` Sami Tolvanen 2015-04-01 13:19 ` Sami Tolvanen 2015-04-03 10:04 ` Herbert Xu 2015-04-03 10:04 ` Herbert Xu 2015-03-25 20:00 ` [PATCH] arm: crypto: Add NEON optimized SHA-256 Jean-Christophe PLAGNIOL-VILLARD 2015-03-25 20:00 ` Jean-Christophe PLAGNIOL-VILLARD
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=20150316162304.GA35408@google.com \ --to=samitolvanen@google.com \ --cc=appro@openssl.org \ --cc=ard.biesheuvel@linaro.org \ --cc=davem@davemloft.net \ --cc=herbert@gondor.apana.org.au \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-crypto@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: linkBe 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.