Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: Nuno Sa <nuno.sa@analog.com>,
	Dragos Bogdan <dragos.bogdan@analog.com>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Olivier Moysan <olivier.moysan@foss.st.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: backend: spelling: continuous -> continuous
Date: Sat, 27 Jul 2024 11:30:07 +0100	[thread overview]
Message-ID: <20240727113007.5fcac093@jic23-huawei> (raw)
In-Reply-To: <20240726-iio-backend-spelling-continuous-v1-1-467c6e3f78ff@baylibre.com>

On Fri, 26 Jul 2024 15:18:40 -0500
David Lechner <dlechner@baylibre.com> wrote:

> This fixes the spelling in IIO_BACKEND_INTERNAL_CONTINUOUS_WAVE.
> 
> Signed-off-by: David Lechner <dlechner@baylibre.com>
Applied
> ---
>  drivers/iio/dac/ad9739a.c     | 2 +-
>  drivers/iio/dac/adi-axi-dac.c | 2 +-
>  include/linux/iio/backend.h   | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/iio/dac/ad9739a.c b/drivers/iio/dac/ad9739a.c
> index 9b1570e788b6..799387f21b9f 100644
> --- a/drivers/iio/dac/ad9739a.c
> +++ b/drivers/iio/dac/ad9739a.c
> @@ -145,7 +145,7 @@ static int ad9739a_buffer_postdisable(struct iio_dev *indio_dev)
>  	struct ad9739a_state *st = iio_priv(indio_dev);
>  
>  	return iio_backend_data_source_set(st->back, 0,
> -					   IIO_BACKEND_INTERNAL_CONTINUOS_WAVE);
> +					   IIO_BACKEND_INTERNAL_CONTINUOUS_WAVE);
>  }
>  
>  static bool ad9739a_reg_accessible(struct device *dev, unsigned int reg)
> diff --git a/drivers/iio/dac/adi-axi-dac.c b/drivers/iio/dac/adi-axi-dac.c
> index 6d56428e623d..e44463f48bf5 100644
> --- a/drivers/iio/dac/adi-axi-dac.c
> +++ b/drivers/iio/dac/adi-axi-dac.c
> @@ -452,7 +452,7 @@ static int axi_dac_data_source_set(struct iio_backend *back, unsigned int chan,
>  	struct axi_dac_state *st = iio_backend_get_priv(back);
>  
>  	switch (data) {
> -	case IIO_BACKEND_INTERNAL_CONTINUOS_WAVE:
> +	case IIO_BACKEND_INTERNAL_CONTINUOUS_WAVE:
>  		return regmap_update_bits(st->regmap,
>  					  AXI_DAC_REG_CHAN_CNTRL_7(chan),
>  					  AXI_DAC_DATA_SEL,
> diff --git a/include/linux/iio/backend.h b/include/linux/iio/backend.h
> index 4e81931703ab..29c4cf0bd761 100644
> --- a/include/linux/iio/backend.h
> +++ b/include/linux/iio/backend.h
> @@ -17,7 +17,7 @@ enum iio_backend_data_type {
>  };
>  
>  enum iio_backend_data_source {
> -	IIO_BACKEND_INTERNAL_CONTINUOS_WAVE,
> +	IIO_BACKEND_INTERNAL_CONTINUOUS_WAVE,
>  	IIO_BACKEND_EXTERNAL,
>  	IIO_BACKEND_DATA_SOURCE_MAX
>  };
> 
> ---
> base-commit: 472438c7e0e2261c6737a8321f46ef176eef1c8f
> change-id: 20240726-iio-backend-spelling-continuous-d6801c838fd8


      reply	other threads:[~2024-07-27 10:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26 20:18 [PATCH] iio: backend: spelling: continuous -> continuous David Lechner
2024-07-27 10:30 ` 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=20240727113007.5fcac093@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=dlechner@baylibre.com \
    --cc=dragos.bogdan@analog.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=olivier.moysan@foss.st.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