[PATCH] iio: st_sensors: fix typo in comment

[PATCH] iio: st_sensors: fix typo in comment

[Ahmad Fatoum]

s/timetamping/timestamping/

Cc: trivial@kernel.org
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 drivers/iio/common/st_sensors/st_sensors_buffer.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/iio/common/st_sensors/st_sensors_buffer.c b/drivers/iio/common/st_sensors/st_sensors_buffer.c
index eee30130ae23..802f9ae04cf4 100644
--- a/drivers/iio/common/st_sensors/st_sensors_buffer.c
+++ b/drivers/iio/common/st_sensors/st_sensors_buffer.c
@@ -57,7 +57,7 @@ irqreturn_t st_sensors_trigger_handler(int irq, void *p)
 	s64 timestamp;
 
 	/*
-	 * If we do timetamping here, do it before reading the values, because
+	 * If we do timestamping here, do it before reading the values, because
 	 * once we've read the values, new interrupts can occur (when using
 	 * the hardware trigger) and the hw_timestamp may get updated.
 	 * By storing it in a local variable first, we are safe.
-- 
2.30.0

Re: [PATCH] iio: st_sensors: fix typo in comment

[Jonathan Cameron]

On Thu, 21 Jan 2021 16:39:44 +0100
Ahmad Fatoum <a.fatoum@pengutronix.de> wrote:

> s/timetamping/timestamping/
> 
> Cc: trivial@kernel.org
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Applied,

Thanks,

Jonathan

> ---
>  drivers/iio/common/st_sensors/st_sensors_buffer.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/iio/common/st_sensors/st_sensors_buffer.c b/drivers/iio/common/st_sensors/st_sensors_buffer.c
> index eee30130ae23..802f9ae04cf4 100644
> --- a/drivers/iio/common/st_sensors/st_sensors_buffer.c
> +++ b/drivers/iio/common/st_sensors/st_sensors_buffer.c
> @@ -57,7 +57,7 @@ irqreturn_t st_sensors_trigger_handler(int irq, void *p)
>  	s64 timestamp;
>  
>  	/*
> -	 * If we do timetamping here, do it before reading the values, because
> +	 * If we do timestamping here, do it before reading the values, because
>  	 * once we've read the values, new interrupts can occur (when using
>  	 * the hardware trigger) and the hw_timestamp may get updated.
>  	 * By storing it in a local variable first, we are safe.