From: Jonathan Cameron <jic23@kernel.org>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: st_sensors: fix typo in comment
Date: Sun, 24 Jan 2021 14:24:52 +0000 [thread overview]
Message-ID: <20210124142452.4739795b@archlinux> (raw)
In-Reply-To: <20210121153945.5499-1-a.fatoum@pengutronix.de>
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.
prev parent reply other threads:[~2021-01-24 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 15:39 [PATCH] iio: st_sensors: fix typo in comment Ahmad Fatoum
2021-01-24 14:24 ` 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=20210124142452.4739795b@archlinux \
--to=jic23@kernel.org \
--cc=a.fatoum@pengutronix.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=trivial@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).