mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: WangYuli <wangyuli@uniontech.com>
Cc: puranjay@kernel.org, lars@metafoo.de,
	Michael.Hennerich@analog.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, puranjay12@gmail.com,
	Jonathan.Cameron@huawei.com
Subject: Re: [PATCH] iio: accel: adxl355: Fix typo "accelaration"
Date: Sat, 19 Oct 2024 13:08:44 +0100	[thread overview]
Message-ID: <20241019130844.0f721bec@jic23-huawei> (raw)
In-Reply-To: <9F137828F9F185FD+20241017092221.361511-1-wangyuli@uniontech.com>

On Thu, 17 Oct 2024 17:22:21 +0800
WangYuli <wangyuli@uniontech.com> wrote:

> There is a spelling mistake of 'accelaration' in comments which
> should be 'acceleration'.
> 
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
Applied.

Thanks,

J
> ---
>  drivers/iio/accel/adxl355_core.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/accel/adxl355_core.c b/drivers/iio/accel/adxl355_core.c
> index eabaefa92f19..7ccd2f653b9b 100644
> --- a/drivers/iio/accel/adxl355_core.c
> +++ b/drivers/iio/accel/adxl355_core.c
> @@ -643,7 +643,7 @@ static irqreturn_t adxl355_trigger_handler(int irq, void *p)
>  	 * The acceleration data is 24 bits and big endian. It has to be saved
>  	 * in 32 bits, hence, it is saved in the 2nd byte of the 4 byte buffer.
>  	 * The buf array is 14 bytes as it includes 3x4=12 bytes for
> -	 * accelaration data of x, y, and z axis. It also includes 2 bytes for
> +	 * acceleration data of x, y, and z axis. It also includes 2 bytes for
>  	 * temperature data.
>  	 */
>  	ret = regmap_bulk_read(data->regmap, ADXL355_XDATA3_REG,


      reply	other threads:[~2024-10-19 12:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  9:22 WangYuli
2024-10-19 12:08 ` 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=20241019130844.0f721bec@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=puranjay12@gmail.com \
    --cc=puranjay@kernel.org \
    --cc=wangyuli@uniontech.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

all inboxes | Powered by JetHome®