From: Herbert Xu <herbert@gondor.apana.org.au>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexey Dobriyan <adobriyan@mail.ru>,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>,
"David S. Miller" <davem@davemloft.net>,
Benjamin Reed <breed@users.sourceforge.net>,
Andy Adamson <andros@citi.umich.edu>,
netdev@vger.kernel.org,
lksctp developers <lksctp-developers@lists.sourceforge.net>,
Bruce Fields <bfields@umich.edu>, Andy Adamson <andros@umich.edu>,
linux-net@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto_free_tfm callers do not need to check for NULL
Date: Wed, 31 Aug 2005 21:57:55 +1000 [thread overview]
Message-ID: <20050831115755.GA3699@gondor.apana.org.au> (raw)
In-Reply-To: <200508302245.55392.jesper.juhl@gmail.com>
On Tue, Aug 30, 2005 at 10:45:54PM +0200, Jesper Juhl wrote:
>
> I've posted similar patches in the past, but was asked to first until the
> short-circuit patch moved from -mm to mainline - and since it is now
> firmly there in 2.6.13 I assume there's no problem there anymore.
> I was also asked previously to make the patch against mainline and not -mm,
> so this patch is against 2.6.13.
Thanks for you work and patience Jesper, this patch looks good to me.
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2005-08-31 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 20:45 Jesper Juhl
2005-08-30 20:49 ` J. Bruce Fields
2005-08-30 21:13 ` Sridhar Samudrala
2005-08-30 21:26 ` Jesper Juhl
2005-08-31 11:57 ` Herbert Xu [this message]
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=20050831115755.GA3699@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=adobriyan@mail.ru \
--cc=andros@citi.umich.edu \
--cc=andros@umich.edu \
--cc=bfields@umich.edu \
--cc=breed@users.sourceforge.net \
--cc=davem@davemloft.net \
--cc=jesper.juhl@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®