From: David Miller Subject: Re: [BUG] SLOB breaks Crypto Date: Wed, 19 May 2010 12:33:25 -0700 (PDT) Message-ID: <20100519.123325.123438307.davem@davemloft.net> References: <1274269236.6930.9930.camel@macbook.infradead.org> <1274278307.11603.1264.camel@calx> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: geert@linux-m68k.org, dwmw2@infradead.org, herbert@gondor.hengli.com.au, penberg@cs.helsinki.fi, ken@codelabs.ch, michael-dev@fami-braun.de, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, anemo@mba.ocn.ne.jp To: mpm@selenic.com Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:39127 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752128Ab0ESTdQ (ORCPT ); Wed, 19 May 2010 15:33:16 -0400 In-Reply-To: <1274278307.11603.1264.camel@calx> Sender: linux-crypto-owner@vger.kernel.org List-ID: From: Matt Mackall Date: Wed, 19 May 2010 09:11:47 -0500 > I still think we should add it to all of them as positive documentation > that this issue has been considered. And then make the kernel not > compile without it so new arch implementors can't miss it. I agree and would even go so far as to suggest that we break all architectures not setting it now.