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 2/3] iio: accel: adxl355: Correct the typo 'accelaration'
Date: Sat, 28 Sep 2024 16:16:31 +0100 [thread overview]
Message-ID: <20240928161631.0182ad73@jic23-huawei> (raw)
In-Reply-To: <739D781F53669A17+ee9db6cf-dca4-4e53-9444-ecdf0b72dfbd@uniontech.com>
On Sun, 22 Sep 2024 19:26:08 +0800
WangYuli <wangyuli@uniontech.com> wrote:
> From 562a6ce3ebbeae03eabdd8fa5c265299ca59560b Mon Sep 17 00:00:00 2001
> From: WangYuli <wangyuli@uniontech.com>
> Date: Sun, 22 Sep 2024 18:45:50 +0800
> Subject: [PATCH 2/3] iio: accel: adxl355: Correct the typo 'accelaration'
>
> There is a spelling mistake of 'accelaration' which should be
> 'acceleration'.
>
> Signed-off-by: WangYuli <wangyuli@uniontech.com>
Patch is fine, but the way it has been sent is not.
We shouldn't be seeing the email header within the body of the patch.
Jonathan
> ---
> 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 0c9225d18fb2..5e682bf079d8 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,
next prev parent reply other threads:[~2024-09-28 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-22 11:18 [PATCH 0/3] treewide: " WangYuli
2024-09-22 11:23 ` [PATCH 1/3] crypto: qat - " WangYuli
2024-09-22 11:28 ` [PATCH 3/3] eth: bnxt: " WangYuli
2024-09-23 14:24 ` [PATCH 1/3] crypto: qat - " Cabiddu, Giovanni
2024-09-22 11:26 ` [PATCH 2/3] iio: accel: adxl355: " WangYuli
2024-09-28 15:16 ` Jonathan Cameron [this message]
2024-09-22 11:35 ` [PATCH 0/3] treewide: " WangYuli
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=20240928161631.0182ad73@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®