From: Jonathan Corbet Subject: Re: [PATCH v2 01/11] crypto: Documentation - crypto API high level spec Date: Mon, 3 Nov 2014 11:44:12 -0500 Message-ID: <20141103114412.78632304@lwn.net> References: <6375771.bx7QqLJLuR@tachyon.chronox.de> <4163724.RCMDlx8dmE@tachyon.chronox.de> <20141103083439.635f5cb6@lwn.net> <4303532.NGaUQ44sQJ@tachyon.chronox.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Cc: Herbert Xu , "David S. Miller" , Marek Vasut , Jason Cooper , Grant Likely , Geert Uytterhoeven , Linux Kernel Developers List , linux-crypto@vger.kernel.org To: Stephan Mueller Return-path: Received: from tex.lwn.net ([70.33.254.29]:38245 "EHLO vena.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752170AbaKCQoP (ORCPT ); Mon, 3 Nov 2014 11:44:15 -0500 In-Reply-To: <4303532.NGaUQ44sQJ@tachyon.chronox.de> Sender: linux-crypto-owner@vger.kernel.org List-ID: On Mon, 03 Nov 2014 15:18:29 +0100 Stephan Mueller wrote: > > 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? See Documentation/kernel-doc-nano-HOWTO.txt for an introduction to the process. This documentation hasn't seen a lot of maintenance recently, but I don't think things have changed too much. Should check that when I get a chance... Thanks, jon