lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 20 May 2007 13:15:50 +1000
From:	Herbert Xu <>
To:	Simon Arlott <>
Cc:	Randy Dunlap <>,
	Linux Kernel Mailing List <>,,
Subject: Re: [PATCH (v2)] crypto: Remove pointless padlock module

On Sat, May 19, 2007 at 08:28:17PM +0100, Simon Arlott wrote:
> It should be a bool that doesn't select anything, the AES and SHA modules 
> will select CRYPTO_ALGAPI. It could also depend on MVIAC3_2 || MVIA_C7 
> instead of X86_32.

Having it as a tristate means that we don't have to duplicate the
dependencies and selects that each padlock algorithm would otherwise
do.  So is there actually a problem with it being a tristate?

Visit Openswan at
Email: Herbert Xu ~{PmV>HI~} <>
Home Page:
PGP Key:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists