public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel•org>
To: Linux Doc Mailing List <linux-doc@vger•kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel•org>,
	linux-kernel@vger•kernel.org, Jonathan Corbet <corbet@lwn•net>,
	"David S. Miller" <davem@davemloft•net>,
	Bartosz Golaszewski <bgolaszewski@baylibre•com>,
	Bjorn Andersson <bjorn.andersson@linaro•org>,
	Jakub Kicinski <kuba@kernel•org>,
	Jonathan Cameron <jic23@kernel•org>, Keerthy <j-keerthy@ti•com>,
	Lars-Peter Clausen <lars@metafoo•de>,
	Linus Walleij <linus.walleij@linaro•org>,
	Marc Kleine-Budde <mkl@pengutronix•de>,
	Mark Brown <broonie@kernel•org>,
	Mathieu Poirier <mathieu.poirier@linaro•org>,
	Ohad Ben-Cohen <ohad@wizery•com>, Peter Rosin <peda@axentia•se>,
	Peter Ujfalusi <peter.ujfalusi@gmail•com>,
	Rob Herring <robh+dt@kernel•org>,
	Ulf Hansson <ulf.hansson@linaro•org>,
	Vinod Koul <vkoul@kernel•org>,
	Wolfgang Grandegger <wg@grandegger•com>,
	devicetree@vger•kernel.org, dmaengine@vger•kernel.org,
	linux-arm-kernel@lists•infradead.org, linux-can@vger•kernel.org,
	linux-gpio@vger•kernel.org, linux-i2c@vger•kernel.org,
	linux-iio@vger•kernel.org, linux-mmc@vger•kernel.org,
	linux-remoteproc@vger•kernel.org, linux-spi@vger•kernel.org,
	linux-usb@vger•kernel.org, netdev@vger•kernel.org
Subject: [PATCH 00/12] Fix broken docs references at next-20210602
Date: Wed,  2 Jun 2021 17:43:06 +0200	[thread overview]
Message-ID: <cover.1622648507.git.mchehab+huawei@kernel.org> (raw)

There are some broken references at today's linux-next with regards
to files inside Documentation/.

Address them.

Mauro Carvalho Chehab (12):
  dt-bindings: power: supply: cpcap-battery: update cpcap-battery.yaml
    reference
  dt-bindings: power: supply: cpcap-charger: update cpcap-charger.yaml
    reference
  dt-bindings: soc: ti: update sci-pm-domain.yaml references
  dt-bindings: clock: update ti,sci-clk.yaml references
  dt-bindings: reset: update ti,sci-reset.yaml references
  dt-bindings: iio: io-channel-mux.yaml: fix a typo
  docs: accounting: update delay-accounting.rst reference
  MAINTAINERS: update faraday,ftrtc010.yaml reference
  MAINTAINERS: update marvell,armada-3700-utmi-phy.yaml reference
  MAINTAINERS: update ti,omap-gpio.yaml reference
  MAINTAINERS: update ti,sci.yaml reference
  MAINTAINERS: update nxp,imx8-jpeg.yaml reference

 Documentation/admin-guide/sysctl/kernel.rst      |  2 +-
 .../devicetree/bindings/dma/ti-edma.txt          |  4 ++--
 .../devicetree/bindings/gpio/gpio-davinci.txt    |  2 +-
 .../devicetree/bindings/i2c/i2c-davinci.txt      |  4 ++--
 .../bindings/iio/multiplexer/io-channel-mux.yaml |  2 +-
 .../devicetree/bindings/mfd/motorola-cpcap.txt   |  4 ++--
 .../devicetree/bindings/mmc/ti-omap-hsmmc.txt    |  4 ++--
 .../devicetree/bindings/net/can/c_can.txt        |  4 ++--
 .../bindings/remoteproc/ti,keystone-rproc.txt    |  4 ++--
 .../devicetree/bindings/spi/spi-davinci.txt      |  2 +-
 .../devicetree/bindings/usb/ti,j721e-usb.yaml    |  2 +-
 .../bindings/usb/ti,keystone-dwc3.yaml           |  2 +-
 MAINTAINERS                                      | 16 ++++++++--------
 13 files changed, 26 insertions(+), 26 deletions(-)

-- 
2.31.1



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2021-06-02 15:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 15:43 Mauro Carvalho Chehab [this message]
2021-06-02 15:43 ` [PATCH 03/12] dt-bindings: soc: ti: update sci-pm-domain.yaml references Mauro Carvalho Chehab
2021-06-02 21:03   ` Rob Herring
2021-06-03 20:08   ` Wolfram Sang
2021-06-02 15:43 ` [PATCH 04/12] dt-bindings: clock: update ti,sci-clk.yaml references Mauro Carvalho Chehab
2021-06-02 21:04   ` Rob Herring
2021-06-03 20:09   ` Wolfram Sang
2021-06-03 20:00 ` [PATCH 00/12] Fix broken docs references at next-20210602 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=cover.1622648507.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel$(echo .)org \
    --cc=bgolaszewski@baylibre$(echo .)com \
    --cc=bjorn.andersson@linaro$(echo .)org \
    --cc=broonie@kernel$(echo .)org \
    --cc=corbet@lwn$(echo .)net \
    --cc=davem@davemloft$(echo .)net \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=dmaengine@vger$(echo .)kernel.org \
    --cc=j-keerthy@ti$(echo .)com \
    --cc=jic23@kernel$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=lars@metafoo$(echo .)de \
    --cc=linus.walleij@linaro$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-can@vger$(echo .)kernel.org \
    --cc=linux-doc@vger$(echo .)kernel.org \
    --cc=linux-gpio@vger$(echo .)kernel.org \
    --cc=linux-i2c@vger$(echo .)kernel.org \
    --cc=linux-iio@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mmc@vger$(echo .)kernel.org \
    --cc=linux-remoteproc@vger$(echo .)kernel.org \
    --cc=linux-spi@vger$(echo .)kernel.org \
    --cc=linux-usb@vger$(echo .)kernel.org \
    --cc=mathieu.poirier@linaro$(echo .)org \
    --cc=mkl@pengutronix$(echo .)de \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=ohad@wizery$(echo .)com \
    --cc=peda@axentia$(echo .)se \
    --cc=peter.ujfalusi@gmail$(echo .)com \
    --cc=robh+dt@kernel$(echo .)org \
    --cc=ulf.hansson@linaro$(echo .)org \
    --cc=vkoul@kernel$(echo .)org \
    --cc=wg@grandegger$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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