Devicetree
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
To: Yahya Toubali <yahya@yahyatoubali.me>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	linux@analog.com (open list:ANALOG DEVICES INC IIO DRIVERS),
	linux-iio@vger.kernel.org (open list:IIO SUBSYSTEM AND DRIVERS),
	devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
	FLATTENED DEVICE TREE BINDINGS),
	linux-kernel@vger.kernel.org (open list)
Subject: Re: [PATCH v3] dt-bindings: iio: dac: fix spelling of 'reference' in adi,ad5791
Date: Sat, 18 Jul 2026 23:05:27 +0100	[thread overview]
Message-ID: <20260718230510.6cb748b1@jic23-huawei> (raw)
In-Reply-To: <20260718165615.1923592-1-yahya@yahyatoubali.me>

On Sat, 18 Jul 2026 17:56:14 +0100
Yahya Toubali <yahya@yahyatoubali.me> wrote:

> Fix misspelling of 'reference' (was 'referance') in the
> vrefp-supply and vrefn-supply descriptions.
> 
> Signed-off-by: Yahya Toubali <yahya@yahyatoubali.me>

Hi Yahya,  I'm not 100% sure why, but none of your postings made it
to my local inbox.  However, they were in patchwork and lore so it
might be a temporary problem my end.

Applied,

Thanks,

Jonathan

> ---
>  Documentation/devicetree/bindings/iio/dac/adi,ad5791.yaml | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/iio/dac/adi,ad5791.yaml b/Documentation/devicetree/bindings/iio/dac/adi,ad5791.yaml
> index 2bd89e0aa46b..80fb98035c6f 100644
> --- a/Documentation/devicetree/bindings/iio/dac/adi,ad5791.yaml
> +++ b/Documentation/devicetree/bindings/iio/dac/adi,ad5791.yaml
> @@ -36,11 +36,11 @@ properties:
>  
>    vrefp-supply:
>      description:
> -      Positive referance input voltage range. From 5v to (vdd - 2.5)
> +      Positive reference input voltage range. From 5v to (vdd - 2.5)
>  
>    vrefn-supply:
>      description:
> -      Negative referance input voltage range. From (vss + 2.5) to 0.
> +      Negative reference input voltage range. From (vss + 2.5) to 0.
>  
>    adi,rbuf-gain2-en:
>      description: Specify to allow an external amplifier to be connected in a
> 
> base-commit: 1229e2e57a5c2980ccd457b9b53ea0eed5a22ab3
> prerequisite-patch-id: c8aee5eb39e3cd6f2b2f28c82163565665288d2a
> prerequisite-patch-id: 60ad32e9f0e74902635d7886b97c4225ac8dc5ce


      reply	other threads:[~2026-07-18 22:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-18 16:56 [PATCH v3] dt-bindings: iio: dac: fix spelling of 'reference' in adi,ad5791 Yahya Toubali
2026-07-18 22:05 ` Jonathan Cameron [this message]

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=20260718230510.6cb748b1@jic23-huawei \
    --to=jonathan.cameron@oss.qualcomm.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@analog.com \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.org \
    --cc=yahya@yahyatoubali.me \
    /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