From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751457AbdAWPYc (ORCPT ); Mon, 23 Jan 2017 10:24:32 -0500 Received: from ms.lwn.net ([45.79.88.28]:44580 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751220AbdAWPYa (ORCPT ); Mon, 23 Jan 2017 10:24:30 -0500 Date: Mon, 23 Jan 2017 08:24:29 -0700 From: Jonathan Corbet To: Matthew Wilcox Cc: Markus Heiser , "linux-doc@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] kernel-doc: Handle returning pointers to pointers Message-ID: <20170123082429.2e48b52f@lwn.net> In-Reply-To: References: <20170123081810.31788-1-mawilcox@microsoft.com> <7E0743A6-066B-4801-8EA7-A4A7CEC70916@darmarit.de> Organization: LWN.net 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 Mon, 23 Jan 2017 15:14:51 +0000 Matthew Wilcox wrote: > > I maintain my own stack of "linuxdoc" with a python version > > of the kernel-doc script (hosted on github). It uses the same > > regexes as the perl version (using a python rewrite here has some > > other benefits, one you will see below). I merged your patch: > > Are there plans to merge that? It feels so odd to have a python script calling a perl script ... I pushed back pretty hard on it last year; my feeling at the time was that the Sphinx transition had enough moving parts as it was. I do think we can reconsider it now, though. It's not as if the perl kerneldoc script is a thing of great beauty in need of preservation. Markus, would you consider sending out a new patch set for review? What I would like to do see is something adding the new script for the Sphinx toolchain, while leaving the DocBook build unchanged, using the old script. We could then delete it once the last template file has moved over. 4.12 would be the probable merge target; it's a big enough change that I'd like to have it in -next for a full development cycle. Thanks, jon