From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965696AbcBQWOG (ORCPT ); Wed, 17 Feb 2016 17:14:06 -0500 Received: from tex.lwn.net ([70.33.254.29]:53758 "EHLO vena.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965535AbcBQWOF (ORCPT ); Wed, 17 Feb 2016 17:14:05 -0500 Date: Wed, 17 Feb 2016 15:14:01 -0700 From: Jonathan Corbet To: Daniel Vetter Cc: Keith Packard , LKML , linux-doc@vger.kernel.org, Jani Nikula Subject: Re: Kernel docs: muddying the waters a bit Message-ID: <20160217151401.3cb82f65@lwn.net> In-Reply-To: References: <20160213145317.247c63c7@lwn.net> <86fuwwcdmd.fsf@hiro.keithp.com> Organization: LWN.net X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 14 Feb 2016 13:27:04 +0100 Daniel Vetter wrote: > One concern/open I have for pro/cons are the hyperlinks from kerneldoc > comments. Currently we have the postproc hack, iirc Jani's patches > generated links native when extracting the kerneldoc. What's the > solution with spinx? So I've been trying to figure out what this refers to. Is this the cross-reference links within the document? When I did my sphinx hack it used a technique that, shall we say, strongly resembles what Jani's patches did. One difference is that Sphinx has the concept of "functions" built into it, so I use function references for those. If you mean links to the wider world, I'm not sure I see that in Jani's patches. It's going to be easily managed in whatever markup language we use, though. jon