public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David McCullough <david_mccullough@au.securecomputing.com>
To: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: ocf-linux-20060331 - Asynchronous Crypto support for linux
Date: Fri, 31 Mar 2006 23:36:12 +1000	[thread overview]
Message-ID: <20060331133612.GB23729@beast> (raw)
In-Reply-To: <20060301042632.GA17290@beast>


Hi all,

A new release of the ocf-linux package is up:

	http://ocf-linux.sourceforge.net/

The changes from the previous release:

	* New Freescale Talitos Driver contributed by Kim Phillips
	* Fixups for some 64bit OS support issues
	* Correctly address safenet lockups on rev 1.0 chips
	* updated openswan patch to 2.4.5rc6

Tested under 2.4.32 and 2.6.16 across multiple architectures,

Cheers,
Davidm

-- 
David McCullough,  david_mccullough@securecomputing.com,   Ph:+61 734352815
Secure Computing - SnapGear  http://www.uCdot.org http://www.cyberguard.com

      reply	other threads:[~2006-03-31 13:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-01  4:26 ocf-linux-20060301 - Asynchronous Crypto support for linux David McCullough
2006-03-31 13:36 ` David McCullough [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=20060331133612.GB23729@beast \
    --to=david_mccullough@au.securecomputing.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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