Received: by 10.192.165.148 with SMTP id m20csp4490744imm; Tue, 8 May 2018 09:14:40 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoXSAohkz8F/9dp7E5mpL5zNG/IS9PXm4qr5E98I+C/HfYV0tmG+lSw3bx5kF5by5SadwRx X-Received: by 2002:a65:6117:: with SMTP id z23-v6mr32569734pgu.72.1525796079955; Tue, 08 May 2018 09:14:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525796079; cv=none; d=google.com; s=arc-20160816; b=X7qS3kuzjb1MXj0VcSjwWfwaE42BYeiRAVJI63hYRgtqxPkbYLxSa/xcb/lDRihifN zqniF2C2honO4upi1o2A15hqs4oepgFlCz83srmqfYscx5Qge8QFmKYlm/ddVy5yGAHO CAr/vOzPlmtxefDyRKBXcc/oFEGG3MCM51sOkJS+MNhgmhBv/K5VN3t3xlsXXTwX0GTy /umLY4V0u27gMvGw8ssN3rWoGzG6czs0HUrcg2Gp8+uuVX6B4W4bF1fpDRqKeLgPzg2v wHLm1Rxc9DJD0vxmZbMkVj5nVMupd5Wu2t/4zgockJ7/WC1seTN+YdZ/T/HGXmGSexAL 5Ixw== 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:arc-authentication-results; bh=j9lPtzfg3ogWLxoO1uxi33CO0Zy0dX31YZnAIrWMFDw=; b=nu3Cvzes2BFstuqW9f2PLibKlLDMzTmxcugTLV8Qikyrul+M26GaS7X7Ol85IVZYvO 1Se//lDYr58TZJusBM62g+e9LM+GbS7vfB5vS+0P0nptCgqUIi05Y2iQmZ+2gyoTNIM+ GGLroxcoBp7sqEH7g6PGLPBGUCNVDA9gpdiIXQWUGtcoSuvqtu9fRJTSd3CZnZgXEhqh 9LVnuzeaAYRm+Bx36CMIAwTuLcUwI1AA+/wcqqOOzAPNpMEyyNg5ifgcumRbgVpq6zJy EaTapkQQQyIORnlkxcNuIzy0fVR5Mp4IRwX5St0R9dfWY6QTaVe5ofUqCi64/idT0wih Mv7g== 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 b96-v6si20791989pli.172.2018.05.08.09.14.24; Tue, 08 May 2018 09:14:39 -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 S932765AbeEHQNt (ORCPT + 99 others); Tue, 8 May 2018 12:13:49 -0400 Received: from ms.lwn.net ([45.79.88.28]:35952 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755237AbeEHQNq (ORCPT ); Tue, 8 May 2018 12:13:46 -0400 Received: from localhost.localdomain (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 7A635318; Tue, 8 May 2018 16:13:44 +0000 (UTC) Date: Tue, 8 May 2018 10:13:42 -0600 From: Jonathan Corbet To: Mauro Carvalho Chehab Cc: Linux Doc Mailing List , Mauro Carvalho Chehab , linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, linux-mtd@lists.infradead.org, linux-fbdev@vger.kernel.org, linux-can@vger.kernel.org, "Luis R. Rodriguez" , linux-iio@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-crypto@vger.kernel.org, Greg Kroah-Hartman , linux-pm@vger.kernel.org Subject: Re: [PATCH 00/18] Fix some build warnings/errors with Sphinx Message-ID: <20180508101342.2bde20ea@lwn.net> In-Reply-To: References: Organization: LWN.net X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.32; 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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 7 May 2018 06:35:36 -0300 Mauro Carvalho Chehab wrote: > I decided to give a try with Sphinx last stable version > (1.17.4), and noticed several issues. The worse one was > with the networking book: a non-standard footnote there > with [*] instead of a number causes it to break PDF building. > > So, I took some spare time to address some warnings all over > the tree, and moved a few text documents to a book. OK, I've applied the ones that seem to make sense for me to take now. There's comments on the firmware one, and I'd rather have Tejun's OK for the cgroup one. The code-comment changes should probably go via the usual maintainers. > I with > I had more time to move the other ones and to solve other > warnings. You and me both - but each step helps! Thanks, jon