From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
alsa-devel@alsa-project.org,
Olivier Moysan <olivier.moysan@st.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-mips@vger.kernel.org,
Andrzej Hajda <a.hajda@samsung.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>,
Sean Wang <sean.wang@mediatek.com>, Jyri Sarha <jsarha@ti.com>,
Mark Brown <broonie@kernel.org>,
linux-mediatek@lists.infradead.org,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-arm-kernel@lists.infradead.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnaud Pouliquen <arnaud.pouliquen@st.com>,
Sandy Huang <hjc@rock-chips.com>,
linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] docs: dt: fix broken links due to txt->yaml renames
Date: Mon, 4 May 2020 19:55:53 +0200 [thread overview]
Message-ID: <20200504175553.jdm7a7aabloevxba@pengutronix.de> (raw)
In-Reply-To: <20200504174522.GA3383@ravnborg.org>
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.
What about adding a check to check_patch?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
next prev parent reply other threads:[~2020-05-04 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 9:30 [PATCH] docs: dt: fix broken links due to txt->yaml renames Mauro Carvalho Chehab
2020-05-04 10:08 ` Mark Brown
2020-05-04 17:28 ` Joe Perches
2020-05-04 17:45 ` Sam Ravnborg
2020-05-04 17:55 ` Uwe Kleine-König [this message]
2020-05-04 19:04 ` Joe Perches
2020-05-05 4:07 ` Rob Herring
2020-05-12 22:58 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200504175553.jdm7a7aabloevxba@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=hjc@rock-chips.com \
--cc=jsarha@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab+huawei@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olivier.moysan@st.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=sean.wang@mediatek.com \
--cc=tsbogend@alpha.franken.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).