Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp3929348pxu; Mon, 30 Nov 2020 13:27:06 -0800 (PST) X-Google-Smtp-Source: ABdhPJyNVGem4sePHS7oCMzVP0V3csTzOvTRHSfe6PuyAHaZ/FyQYnydHPy3+UpXJqtKuqxgEx5V X-Received: by 2002:a05:6402:2d4:: with SMTP id b20mr3878979edx.237.1606771626438; Mon, 30 Nov 2020 13:27:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606771626; cv=none; d=google.com; s=arc-20160816; b=HXShYiy3cJfFBVbDpHcW+O1Th2cxsMM9fmEBbvM4S9vjXzHaeFch/+R06RjzEEeZm8 IL1g5m6okuC2uioeKRllbYg08Dw/V7GpCJ5UFn/3urmX50mevZiSPugeG8HR7YYC2Ybd hdrrJ0Xc9MXjP92E9eK8oCQYiFoCa4VaExYTvwkUqXMfotl9Yog0mwjIVfw8I8no3PR1 IRIY6z5NSGJfppMfKcCKAqvqE1+1tVLY43q040XK9AOV1CwOomAsd46GGuIbvSCALnHo GKHbJXXiaX0XaFDM6Cpk1gkb/DUkS/rpDWMAfQEMWwgppuwEZn+NzC0DcTtd+KLjErl6 kOng== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=d5tvs83oFW4im1OKjVRJ8NJlOJz94JQzMMuUHTLUqis=; b=qoOosT1O4n/fzm+Z5cDeFAdbQncVKoAEHZwmaG6kLIY34Ulp3bl/F29N8j4qI8gTD8 jtKK+/q0ATqtR0vt2pa4whurNIbkmYmI9fogqLzfdHDBtWjNk3Jp4iBFP2KQprUQyMPC bfzMmrVJPui5KR2NNY6duYZY9LnJWMBe+zHStRslMxzjIkazLnRiyTGrht1jVyTUhPzo lHs4Z/h3LtZV3yID2tH/ixblQhpVmjChJL4RSLlhT754BRods65rQmGoo10fLsKnNN8E AQDQ/aRP7k0yBd2LeTRW4yCY+6olW3u2M4AxqRCzp5SWcs9vupCIzfdfUEbUrsvWJXwK iPUQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bo5si11944680ejb.102.2020.11.30.13.26.43; Mon, 30 Nov 2020 13:27:06 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388579AbgK3VYq (ORCPT + 99 others); Mon, 30 Nov 2020 16:24:46 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55976 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387645AbgK3VYq (ORCPT ); Mon, 30 Nov 2020 16:24:46 -0500 Received: from ms.lwn.net (ms.lwn.net [IPv6:2600:3c01:e000:3a1::42]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 05586C0613CF; Mon, 30 Nov 2020 13:24:06 -0800 (PST) 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 802CF735; Mon, 30 Nov 2020 21:24:05 +0000 (UTC) Date: Mon, 30 Nov 2020 14:24:04 -0700 From: Jonathan Corbet To: "=?UTF-8?B?TsOtY29sYXM=?= F. R. A. Prado" Cc: Rob Herring , Mauro Carvalho Chehab , devicetree@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, lkcamp@lists.libreplanetbr.org, andrealmeid@collabora.com Subject: Re: [PATCH] docs: dt: Use full path to enable cross-reference Message-ID: <20201130142404.6ef6689e@lwn.net> In-Reply-To: <20201123121333.59274-1-nfraprado@protonmail.com> References: <20201123121333.59274-1-nfraprado@protonmail.com> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 23 Nov 2020 12:13:46 +0000 NĂ­colas F. R. A. Prado wrote: > Use full path to reference writing-schema.rst so that it becomes a > cross-reference. > > Signed-off-by: NĂ­colas F. R. A. Prado > --- > > Hi Jon, > > do you think this would be the way to go, or should we instead extend automarkup > to work on relative paths to doc pages, so that this reference would work as is? Sorry, I missed this before ... dunno. I suppose that recognizing relative paths would be a friendly gesture toward our documentation writers and might be worth doing. Either way, it occurs to me that automarkup should check to see whether the file actually exists and complain if it doesn't. For now, I'll apply this one, though. Thanks, jon