Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp2658897ybb; Fri, 27 Mar 2020 09:42:10 -0700 (PDT) X-Google-Smtp-Source: ADFU+vv1eP6xvDHzhQZ3KmK7ypV1POqvoVqa9Hl9nkv0fhkHvzj3s8R5giyMmYwxhOG9Mjs4vSB4 X-Received: by 2002:a9d:c69:: with SMTP id 96mr11839326otr.77.1585327330216; Fri, 27 Mar 2020 09:42:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585327330; cv=none; d=google.com; s=arc-20160816; b=zfBgpV3aCJ8UhkDZSdOIo+vz2pSy/ZigIFyQTemS5CentgEOOHJjDyYwkiRjqwzDe+ mph6LduMOgMjX9DwGU7+DyKmD2efbPY8sjPL2AwiXE1psaF/VYuXWWNwecG/GCWQaflA c6iwB45Nfjc1cXHPuM0Ue+hzB2eZb17DhdCftga7RMgiJJLHADp3mdQGDcvHz2lUcXmF eHlcPodrscC08YOLgS+v13VPsQfyd015uqnaSA1kX7+KXXCn86ySNvc7eDNmfrUz6LJo 1S7lB44aukaaiAV5SMUscPE9Q+s8RQyUQuwtIMfm/8tcdMy6zDivt80iBNI7BWJ2QQcx OftA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=MvmM8Z6NTNku/4MERY8QV6/Fia9yOLD4FZvZcx6TwhI=; b=Lb6xQ+eiS8pbIbsQo4vizKuNtAvCgplcbrcEveB07TVBQyG7eXiD8f2rLfQK+9UZXM aE+/Aw02gMPqg7TcMuvKaSAZrcp6661FdSOxPM92Igx8EIOBJmlwCyyhWr2lkSOq/Zku fRTCenw0MGk9ob3SNSu+9/rxSVXCvC24nzaKgXSOGw0W/aKsXWJO9pWRZT1yn86pri0f U8NuSt3VLbncGYpNtURfsbwOvmVPuXv9YNAKX8FleoE3jOK9ODchiVO337knrWzBX8Qk /DFs8JhXpJEbT7QWL6hTBuMXT0WC7hugrkW+WVlGpwR1V8ep1t3KZTD6C68BpijKliBl iscA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h20si2443187oie.28.2020.03.27.09.41.54; Fri, 27 Mar 2020 09:42:10 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727771AbgC0Ql2 (ORCPT + 99 others); Fri, 27 Mar 2020 12:41:28 -0400 Received: from ms.lwn.net ([45.79.88.28]:47238 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727593AbgC0Ql2 (ORCPT ); Fri, 27 Mar 2020 12:41:28 -0400 Received: from lwn.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 03A11537; Fri, 27 Mar 2020 16:41:27 +0000 (UTC) Date: Fri, 27 Mar 2020 10:41:26 -0600 From: Jonathan Corbet To: Jani Nikula Cc: peter@bikeshed.quignogs.org.uk, Matthew Wilcox , linux-kernel@vger.kernel.org, Greg Kroah-Hartman , "Rafael J. Wysocki" , linux-doc@vger.kernel.org Subject: Re: [PATCH v3 0/1] Compactly make code examples into literal blocks Message-ID: <20200327104126.667b5d5b@lwn.net> In-Reply-To: <87imiqghop.fsf@intel.com> References: <20200326192947.GM22483@bombadil.infradead.org> <20200326195156.11858-1-peter@bikeshed.quignogs.org.uk> <87imiqghop.fsf@intel.com> 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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 27 Mar 2020 13:28:54 +0200 Jani Nikula wrote: > IMHO the real problem is kernel-doc doing too much preprocessing on the > input, preventing us from doing what would be the sensible thing in > rst. The more we try to fix the problem by adding more kernel-doc > processing, the further we dig ourselves into this hole. > > If kernel-doc didn't have its own notion of section headers, such as > "example:", we wouldn't have this problem to begin with. We could just > use the usual rst construct; "example::" followed by an indented block. > > I'm not going to stand in the way of the patch, but I'm telling you, > this is going to get harder, not easier, on this path. I agree with you in principle. The problem, of course, is that this is a legacy gift from before the RST days and it will be hard to change. A quick grep shows that the pattern: * Example: appears nearly 100 times in current kernels. It is not inconceivable to make a push to get rid of all of those, turning them into ordinary RST syntax - especially since not all of those are actually kerneldoc comments. The same quick grep says that "returns?:" appears about 10,000 times. *That* will be painful to change, and I can only imagine that some resistance would have to be overcome at some point. So what do folks think we should do? :) I want to ponder on this for a bit. Peter, that may mean that I hold this patch past the 5.7 merge window, which perhaps makes sense at this point anyway, sorry. But I really would like to push things into a direction that moves us away from gnarly perl hacks and toward something more maintainable in the long term. Thanks, jon