From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261218AbVDSIgS (ORCPT ); Tue, 19 Apr 2005 04:36:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261191AbVDSIgS (ORCPT ); Tue, 19 Apr 2005 04:36:18 -0400 Received: from mail.dif.dk ([193.138.115.101]:33156 "EHLO saerimmer.dif.dk") by vger.kernel.org with ESMTP id S261188AbVDSIgN (ORCPT ); Tue, 19 Apr 2005 04:36:13 -0400 Date: Tue, 19 Apr 2005 10:39:12 +0200 (CEST) From: Jesper Juhl To: Herbert Xu Cc: "David S. Miller" , James Morris , linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] crypto: resource release functions ought to check for NULL (crypto_free_tfm) In-Reply-To: <20050419082048.GA5629@gondor.apana.org.au> Message-ID: References: <20050418114925.GA6854@gondor.apana.org.au> <20050419082048.GA5629@gondor.apana.org.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 19 Apr 2005, Herbert Xu wrote: > On Mon, Apr 18, 2005 at 05:23:31PM +0200, Jesper Juhl wrote: > > > > Next step is to then clean up the callers of crypto_free_tfm so they no > > longer do the redundant NULL check. Below is a patch to do that. > > Please wait until the free_tfm change gets into the kernel and then > submit this to the subsystem maintainers, which would all be Dave > in this case :) Sure thing, not a problem. -- Jesper