linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Mauro Carvalho Chehab" <mchehab+huawei@kernel.org>,
	"Linux Doc Mailing List" <linux-doc@vger.kernel.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
	"Sudeep Holla" <sudeep.holla@arm.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Andy Gross" <agross@kernel.org>,
	"Bjorn Andersson" <bjorn.andersson@linaro.org>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>, "Jyri Sarha" <jsarha@ti.com>,
	"Tomi Valkeinen" <tomi.valkeinen@ti.com>,
	"David Airlie" <airlied@linux.ie>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Jacek Anaszewski" <jacek.anaszewski@gmail.com>,
	"Pavel Machek" <pavel@ucw.cz>, "Dan Murphy" <dmurphy@ti.com>,
	"Stuart Yoder" <stuyoder@gmail.com>,
	"Laurentiu Tudor" <laurentiu.tudor@nxp.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Joel Stanley" <joel@jms.id.au>,
	"Kevin Hilman" <khilman@baylibre.com>,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
	"Alexandre Torgue" <alexandre.torgue@st.com>,
	"Zhang Rui" <rui.zhang@intel.com>,
	"Daniel Lezcano" <daniel.lezcano@linaro.org>,
	"Amit Kucheria" <amit.kucheria@verdurent.com>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linux-leds@vger.kernel.org,
	linux-aspeed@lists.ozlabs.org, openbmc@lists.ozlabs.org,
	linux-gpio@vger.kernel.org, linux-amlogic@lists.infradead.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH 2/7] docs: dt: fix several broken references due to renames
Date: Mon, 24 Feb 2020 10:37:53 +1030	[thread overview]
Message-ID: <41551c09-5443-4980-9c6f-6bc7f48aa356@www.fastmail.com> (raw)
In-Reply-To: <83c5df4acbbe0fa55a1d58d4c4a435b51cd2a7ad.1582361737.git.mchehab+huawei@kernel.org>



On Sat, 22 Feb 2020, at 19:30, Mauro Carvalho Chehab wrote:
> Several DT references got broken due to txt->yaml conversion.
> 
> Those are auto-fixed by running:
> 
> 	scripts/documentation-file-ref-check --fix
> 
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> ---
...
>  .../bindings/pinctrl/aspeed,ast2400-pinctrl.yaml          | 2 +-
>  .../bindings/pinctrl/aspeed,ast2500-pinctrl.yaml          | 2 +-
>  .../bindings/pinctrl/aspeed,ast2600-pinctrl.yaml          | 2 +-

Acked-by: Andrew Jeffery <andrew@aj.id.au>

  reply	other threads:[~2020-02-24  0:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-22  9:00 [PATCH 0/7] Some cross-reference fixes due to fixes renames Mauro Carvalho Chehab
2020-02-22  9:00 ` [PATCH 1/7] scripts: documentation-file-ref-check: improve :doc: handling Mauro Carvalho Chehab
2020-02-22  9:00 ` [PATCH 2/7] docs: dt: fix several broken references due to renames Mauro Carvalho Chehab
2020-02-24  0:07   ` Andrew Jeffery [this message]
2020-02-24 13:02   ` Dan Murphy
2020-02-24 14:55   ` Amit Kucheria
2020-02-24 18:14   ` Rob Herring
2020-02-27  9:16   ` Daniel Lezcano
2020-02-22  9:00 ` [PATCH 3/7] docs: fix broken references to text files Mauro Carvalho Chehab
2020-02-22 17:51   ` Daniel Vetter
2020-02-24  9:26   ` Federico Vaga
2020-03-25  2:42   ` Stephen Boyd
2020-02-22  9:00 ` [PATCH 4/7] docs: adm1177: fix a broken reference Mauro Carvalho Chehab
2020-02-22 15:48   ` Guenter Roeck
2020-02-22  9:00 ` [PATCH 5/7] docs: fix broken references for ReST files that moved around Mauro Carvalho Chehab
2020-02-23  8:12   ` Paolo Bonzini
2020-02-22  9:00 ` [PATCH 6/7] docs: remove nompx kernel parameter and intel_mpx from index.rst Mauro Carvalho Chehab
2020-02-24 17:30   ` Dave Hansen
2020-02-25 10:06     ` Jonathan Corbet
2020-02-22  9:00 ` [PATCH 7/7] docs: gpu: i915.rst: fix warnings due to file renames Mauro Carvalho Chehab
2020-02-25 23:36   ` Rodrigo Vivi
2020-02-25 10:05 ` [PATCH 0/7] Some cross-reference fixes due to fixes renames Jonathan Corbet

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=41551c09-5443-4980-9c6f-6bc7f48aa356@www.fastmail.com \
    --to=andrew@aj.id.au \
    --cc=agross@kernel.org \
    --cc=airlied@linux.ie \
    --cc=alexandre.torgue@st.com \
    --cc=amit.kucheria@verdurent.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=corbet@lwn.net \
    --cc=daniel.lezcano@linaro.org \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jacek.anaszewski@gmail.com \
    --cc=joel@jms.id.au \
    --cc=jsarha@ti.com \
    --cc=khilman@baylibre.com \
    --cc=laurentiu.tudor@nxp.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mchehab+huawei@kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=p.zabel@pengutronix.de \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=sboyd@kernel.org \
    --cc=stuyoder@gmail.com \
    --cc=sudeep.holla@arm.com \
    --cc=tomi.valkeinen@ti.com \
    /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).