Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933180AbbLHIK7 (ORCPT ); Tue, 8 Dec 2015 03:10:59 -0500 Received: from mail-wm0-f50.google.com ([74.125.82.50]:35270 "EHLO mail-wm0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755327AbbLHIK5 (ORCPT ); Tue, 8 Dec 2015 03:10:57 -0500 From: LABBE Corentin To: clabbe.montjoie@gmail.com, davem@davemloft.net, geert+renesas@glider.be, herbert@gondor.apana.org.au, luis@debethencourt.com, maxime.ripard@free-electrons.com, thomas.lendacky@amd.com Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 0/4] crypto: add precalculated hash for zero message length Date: Tue, 8 Dec 2015 09:10:49 +0100 Message-Id: <1449562253-13846-1-git-send-email-clabbe.montjoie@gmail.com> X-Mailer: git-send-email 2.4.10 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1367 Lines: 36 Hello Some crypto drivers cannot process empty data message and so rely on precalculated hash. This patch series add precalculated hash in headers and make the drivers use them. Using those precalculated hash make some additionnal constify patch necessary. Changes since v1 - Moved arrays from headers to c file and made them EXPORT. LABBE Corentin (4): crypto: hash: add zero length message hash for shax and md5 crypto: niagara: Use precalculated hash from headers crypto: ccp: Use precalculated hash from headers crypto: ux500: Use precalculated hash from headers crypto/md5.c | 6 ++++++ crypto/sha1_generic.c | 7 +++++++ crypto/sha256_generic.c | 16 ++++++++++++++ drivers/crypto/ccp/ccp-ops.c | 39 +++++++---------------------------- drivers/crypto/n2_core.c | 33 ++++++----------------------- drivers/crypto/ux500/hash/hash_core.c | 20 ++---------------- include/crypto/md5.h | 2 ++ include/crypto/sha.h | 6 ++++++ 8 files changed, 53 insertions(+), 76 deletions(-) -- 2.4.10 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/