[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 4 May 2020 23:07:57 -0500
From: Rob Herring <robh+dt@...nel.org>
To: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>, Sam Ravnborg <sam@...nborg.org>
Cc: Linux-ALSA <alsa-devel@...a-project.org>,
Olivier Moysan <olivier.moysan@...com>,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
David Airlie <airlied@...ux.ie>,
dri-devel <dri-devel@...ts.freedesktop.org>,
"open list:MIPS" <linux-mips@...r.kernel.org>,
Andrzej Hajda <a.hajda@...sung.com>,
Jonathan Corbet <corbet@....net>,
Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
devicetree@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
Sean Wang <sean.wang@...iatek.com>, Jyri Sarha <jsarha@...com>,
Mark Brown <broonie@...nel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@...ts.infradead.org>,
Matthias Brugger <matthias.bgg@...il.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Arnaud Pouliquen <arnaud.pouliquen@...com>,
Sandy Huang <hjc@...k-chips.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@...r.kernel.org>,
netdev <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH] docs: dt: fix broken links due to txt->yaml renames
On Mon, May 4, 2020 at 12:56 PM Uwe Kleine-König
<u.kleine-koenig@...gutronix.de> 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
Powered by blists - more mailing lists