From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F3EB7C47256 for ; Tue, 5 May 2020 04:08:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D2C08206B8 for ; Tue, 5 May 2020 04:08:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1588651697; bh=uzzMCgqE/O5IIYjUlJGPkxkNrxePxpFGbx62v87B1yk=; h=References:In-Reply-To:From:Date:Subject:To:Cc:List-ID:From; b=RPBGO8jVGwIQ34fm9+7vTY1fBurltH2CfGDniSDvEZjF1sHrhSkugga0v7KIDu8l7 owuHdqEMqIPX6BRHxouSMcZgNDfz1+1VpdhlLVSOuVs2pREWs9hcYbLCPImNBmPz9h 8SQXkddtfC9tevoqxK2g0WYxzgnykBgGgwvciFgk= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726222AbgEEEIL (ORCPT ); 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-Google-Smtp-Source: APiQypKr0Hhrl0+e44U31hazXs0o4bScaIuGYf4nCgkUWwDdJ4zYt2nRLPemlwjIE7S1TGeNHXWRAj+I7RpOjlh+8dk= 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