linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Linux Doc Mailing List" <linux-doc@vger.kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 18/24] include/linux/iio/dac/mcp4725.h: update a microchip,mcp4725.yaml ref
Date: Wed, 13 Jan 2021 11:59:19 +0100	[thread overview]
Message-ID: <ae1bc39a6c064bbce186a720a84a4f325bc2438c.1610535350.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1610535349.git.mchehab+huawei@kernel.org>

Changeset 6ced946a4bba ("dt-bindings:iio:dac:microchip,mcp4725 yaml conversion")
renamed: Documentation/devicetree/bindings/iio/dac/mcp4725.txt
to: Documentation/devicetree/bindings/iio/dac/microchip,mcp4725.yaml.

Update its cross-reference accordingly.

Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
 include/linux/iio/dac/mcp4725.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/iio/dac/mcp4725.h b/include/linux/iio/dac/mcp4725.h
index e9801c8d49c0..1f7e53c506b6 100644
--- a/include/linux/iio/dac/mcp4725.h
+++ b/include/linux/iio/dac/mcp4725.h
@@ -15,7 +15,7 @@
  * @vref_buffered: Controls buffering of the external reference voltage.
  *
  * Vref related settings are available only on MCP4756. See
- * Documentation/devicetree/bindings/iio/dac/mcp4725.txt for more information.
+ * Documentation/devicetree/bindings/iio/dac/microchip,mcp4725.yaml for more information.
  */
 struct mcp4725_platform_data {
 	bool use_vref;
-- 
2.29.2


  parent reply	other threads:[~2021-01-13 11:02 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13 10:59 [PATCH 00/24] Fix broken file docs cross-references Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 01/24] MAINTAINERS: update adi,ad5758.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 02/24] MAINTAINERS: update fsl,dpaa2-console.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 03/24] MAINTAINERS: update st,hts221.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 04/24] MAINTAINERS: update dpot-dac.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 05/24] MAINTAINERS: update envelope-detector.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 06/24] MAINTAINERS: update current-sense-amplifier.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 07/24] MAINTAINERS: update current-sense-shunt.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 08/24] MAINTAINERS: update voltage-divider.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 09/24] MAINTAINERS: update mtk-sd.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 10/24] MAINTAINERS: update atmel,sama5d2-adc.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 11/24] MAINTAINERS: update pni,rm3100.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 12/24] MAINTAINERS: update renesas,rcar-gyroadc.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 13/24] MAINTAINERS: update st,lsm6dsx.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 14/24] MAINTAINERS: update st,vl53l0x.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 15/24] MAINTAINERS: update ti,dac7612.yaml reference Mauro Carvalho Chehab
2021-01-13 10:59 ` [PATCH 16/24] Documentation/hwmon/ina2xx.rst: update ti,ina2xx.yaml reference Mauro Carvalho Chehab
2021-01-21 19:28   ` Guenter Roeck
2021-01-13 10:59 ` [PATCH 17/24] arch/Kconfig: update unaligned-memory-access.rst reference Mauro Carvalho Chehab
2021-01-13 18:13   ` Kees Cook
2021-01-13 10:59 ` Mauro Carvalho Chehab [this message]
2021-01-13 15:52   ` [PATCH 18/24] include/linux/iio/dac/mcp4725.h: update a microchip,mcp4725.yaml ref Jonathan Cameron
2021-01-13 10:59 ` [PATCH 19/24] doc: update rcu_dereference.rst reference Mauro Carvalho Chehab
2021-01-13 15:12   ` Paul E. McKenney
2021-01-13 10:59 ` [PATCH 20/24] ASoC: audio-graph-card: update audio-graph-card.yaml reference Mauro Carvalho Chehab
2021-01-25 19:34   ` Rob Herring
2021-01-13 10:59 ` [PATCH 21/24] dt-bindings: display: mediatek: update mediatek,dpi.yaml reference Mauro Carvalho Chehab
2021-01-25 19:35   ` [PATCH 21/24] dt-bindings: display: mediatek: update mediatek, dpi.yaml reference Rob Herring
2021-01-13 10:59 ` [PATCH 22/24] dt-bindings: memory: mediatek: update mediatek,smi-larb.yaml references Mauro Carvalho Chehab
2021-01-25 19:36   ` [PATCH 22/24] dt-bindings: memory: mediatek: update mediatek, smi-larb.yaml references Rob Herring
2021-01-13 10:59 ` [PATCH 23/24] dt-bindings:iio:adc: update adc.yaml reference Mauro Carvalho Chehab
2021-01-13 15:53   ` Jonathan Cameron
2021-01-25 19:36   ` Rob Herring
2021-01-13 10:59 ` [PATCH 24/24] dt-bindings: phy: update phy-cadence-sierra.yaml reference Mauro Carvalho Chehab
2021-01-13 14:17   ` Vinod Koul

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=ae1bc39a6c064bbce186a720a84a4f325bc2438c.1610535350.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /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).