Received: by 2002:a25:23cc:0:0:0:0:0 with SMTP id j195csp272005ybj; Mon, 4 May 2020 21:09:02 -0700 (PDT) X-Google-Smtp-Source: APiQypLGzlbUyLnijRL793kyVm0A4Bbit9cuab8wAOMEIiMGNSLPpPD86iuhTpoj+j/WH3baT9ih X-Received: by 2002:a17:906:3e96:: with SMTP id a22mr966718ejj.232.1588651742268; Mon, 04 May 2020 21:09:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588651742; cv=none; d=google.com; s=arc-20160816; b=C2fBZlavqiDKLdu7hGU4iukQrlgcWnDsgRAXAoPciv6XoJHzlqPbZ5ddPRgcRixFN/ ct7f7OG23Z/SUrpUK1Sh3VDXKnscGjqxS/7GIVjckJx/nSYAbp6B1S2+qV3hKCikNqKq XHPVP95Sr2bLME8UwCPnk208jsVJF8KUNH53VKhsfy1fZme3f302HLSWmxl7iPRlRa1E 06m2HKtx5W0o0X/iOT4ZUuk/8rEfiaiS+uRo60OLaWP44uipODzPBEWEHh1jfnecd/ds oLsqwzXPvwMnEqfM5jrDfgPfpuzf5VW+ViE8FjvCJqrrEZdZdGZgHM3k2ytur4ODFYTI BywQ== 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:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=DYU3Se+m5qeVce1JBRZ5X8Ge9ZqBrvScs141FTGnGTU=; b=oj8bQeq9stTxCqscWqn0zw4JY++oRZY5dYqZmgVY2ZwHXFY2YOPrHxPjnk7ttYlr3t EoU0tl+ngYjzA21KVVHlt9Q9AW79+C0TMZ0as9vSRissgvVZiToe0+W10SbOIVIAPhyK 4l/cHUZJ/RgZMc2hXQprh554oerqcfJFBkLCepmjFNW5a7+NZuPSXyRxxK15/+FCC90s yb9WiFL+/5ip9I/UyRoU7nZGqitVQ+0048UzRFSHyEE66Q31UtG4+zd6/mX/3Q+ijDrL 5TApwytt7oyLYDjsNNyFS3FlKtbWMPEA5W2QFGI2JaA0bHcseo+XVNc0+bYYt+l7hZ32 VgIg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="BN6Cy/3H"; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g8si570337edn.504.2020.05.04.21.08.18; Mon, 04 May 2020 21:09:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b="BN6Cy/3H"; spf=pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-bluetooth-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725915AbgEEEIL (ORCPT + 99 others); Tue, 5 May 2020 00:08:11 -0400 Received: from mail.kernel.org ([198.145.29.99]:45308 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725272AbgEEEIL (ORCPT ); Tue, 5 May 2020 00:08:11 -0400 Received: from mail-ot1-f54.google.com (mail-ot1-f54.google.com [209.85.210.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 319202087E; Tue, 5 May 2020 04:08:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1588651690; bh=uzzMCgqE/O5IIYjUlJGPkxkNrxePxpFGbx62v87B1yk=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=BN6Cy/3HpCwbAGqGdvC+qqnnmWcpBeTMOV+avy7c5MqADF8o2RkgcRkJzIQXdsCsk 1Afk3jIt/KQM3TnQcStiKfqzuLsewX65wxQohWJds/+9oXyCCJshgXhqgUpXBb3dvp Pj9E/11iNOGPIQykmHB/KEKg0M4b5I2GMOZkNt/o= Received: by mail-ot1-f54.google.com with SMTP id m13so561394otf.6; Mon, 04 May 2020 21:08:10 -0700 (PDT) X-Gm-Message-State: AGi0PuYCc8W08LyWksuW5sQZqz/19WrYFFaUhJea7EHP7Nd0bFUJ8bMP TH24vvr7k6O4ssDpVm8Cn3ceMFQOC52xr3mHaw== X-Received: by 2002:a9d:7d85:: with SMTP id j5mr690540otn.107.1588651689440; Mon, 04 May 2020 21:08:09 -0700 (PDT) MIME-Version: 1.0 References: <967df5c3303b478b76199d4379fe40f5094f3f9b.1588584538.git.mchehab+huawei@kernel.org> <20200504174522.GA3383@ravnborg.org> <20200504175553.jdm7a7aabloevxba@pengutronix.de> In-Reply-To: <20200504175553.jdm7a7aabloevxba@pengutronix.de> From: Rob Herring Date: Mon, 4 May 2020 23:07:57 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] docs: dt: fix broken links due to txt->yaml renames To: =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= , Sam Ravnborg Cc: Linux-ALSA , Olivier Moysan , Linux Doc Mailing List , David Airlie , dri-devel , "open list:MIPS" , Andrzej Hajda , Jonathan Corbet , Mauro Carvalho Chehab , "open list:ARM/Rockchip SoC..." , devicetree@vger.kernel.org, Liam Girdwood , Sean Wang , Jyri Sarha , Mark Brown , "moderated list:ARM/Mediatek SoC support" , Matthias Brugger , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , Thomas Bogendoerfer , Greg Kroah-Hartman , Arnaud Pouliquen , Sandy Huang , "linux-kernel@vger.kernel.org" , "open list:BLUETOOTH DRIVERS" , netdev , "David S. Miller" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-bluetooth-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org On Mon, May 4, 2020 at 12:56 PM Uwe Kleine-K=C3=B6nig wrote: > > Hi Sam, > > On Mon, May 04, 2020 at 07:45:22PM +0200, Sam Ravnborg wrote: > > On Mon, May 04, 2020 at 11:30:20AM +0200, Mauro Carvalho Chehab wrote: > > > There are some new broken doc links due to yaml renames > > > at DT. Developers should really run: > > > > > > ./scripts/documentation-file-ref-check > > > > > > in order to solve those issues while submitting patches. > > Would love if some bot could do this for me on any patches that creates > > .yaml files or so. > > I know I will forget this and it can be automated. > > If I get a bot mail that my patch would broke a link I would > > have it fixed before it hits any tree. I can probably add this to what I'm already checking. Not completely automated though as it depends on me to review before sending. > What about adding a check to check_patch? That would be the best way to get submitters to do this. Rob