Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932965Ab3EORIB (ORCPT ); Wed, 15 May 2013 13:08:01 -0400 Received: from mail-ie0-f172.google.com ([209.85.223.172]:40109 "EHLO mail-ie0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759551Ab3EORH7 (ORCPT ); Wed, 15 May 2013 13:07:59 -0400 MIME-Version: 1.0 In-Reply-To: <1368611522-9984-13-git-send-email-lee.jones@linaro.org> References: <1368611522-9984-1-git-send-email-lee.jones@linaro.org> <1368611522-9984-13-git-send-email-lee.jones@linaro.org> Date: Wed, 15 May 2013 19:07:58 +0200 Message-ID: Subject: Re: [PATCH 12/39] crypto: ux500/hash - Prepare clock before enabling it From: Linus Walleij To: Lee Jones Cc: "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Felipe Balbi , "linux-usb@vger.kernel.org" , "linux-crypto@vger.kernel.org" , "David S. Miller" , Herbert Xu , Vinod Koul , Arnd Bergmann , Linus WALLEIJ , Srinidhi KASAGAR , Andreas Westin Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1080 Lines: 29 On Wed, May 15, 2013 at 11:51 AM, Lee Jones wrote: > If we fail to prepare the ux500-hash clock before enabling it the > platform will fail to boot. Here we insure this happens. > > Cc: Herbert Xu > Cc: David S. Miller > Cc: Andreas Westin > Cc: linux-crypto@vger.kernel.org > Acked-by: Arnd Bergmann > Acked-by: Ulf Hansson > Signed-off-by: Lee Jones This patch seems to be totally independent of the other stuff in the patch series, and it even seems like an -rc fix to me (I don't think the crypto device works without this). This should go into the crypto tree? Else please convince Herbert to give his ACK on this before I apply it. Yours, Linus Walleij -- 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/