lists.openwall.net | 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 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 8 Nov 2014 21:54:20 -0500 From: Jason Cooper <jason@...edaemon.net> To: Stephan Mueller <smueller@...onox.de> Cc: Jonathan Corbet <corbet@....net>, Herbert Xu <herbert@...dor.apana.org.au>, "David S. Miller" <davem@...emloft.net>, Marek Vasut <marex@...x.de>, Grant Likely <grant.likely@...retlab.ca>, Geert Uytterhoeven <geert@...ux-m68k.org>, Linux Kernel Developers List <linux-kernel@...r.kernel.org>, linux-crypto@...r.kernel.org Subject: Re: [PATCH v2 01/11] crypto: Documentation - crypto API high level spec Stephan, On Mon, Nov 03, 2014 at 03:18:29PM +0100, Stephan Mueller wrote: > Am Montag, 3. November 2014, 08:34:39 schrieb Jonathan Corbet: > > These are all useful. But I wonder if it would be worth the effort to turn > > this inti a proper docbook document that automatically has everything > > together in one place? > > How do you suggest that is done? The API comments in the header file follow > the Doxygen style. Note, Jason Cooper raised the concern that an API > documentation separate from the code will surely deviate from the code > relatively fast (although I do not really fear that as the kernel crypto API > seems to be quite stable over the last years). Agreed. My primary concern was adding it in such a way which facilitates maintenance and keeping it in sync with the code. But as you say, the crypto API doesn't change much. thx, Jason. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists