From: Jonathan Cameron <jic23@kernel.org>
To: Flavio Suligoi <f.suligoi@asem.it>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Benson Leung <bleung@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Guenter Roeck <groeck@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
Lee Jones <lee.jones@linaro.org>,
Sebastian Reichel <sre@kernel.org>,
Fabien Lahoudere <fabien.lahoudere@collabora.com>,
<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] iio: common: fix spelling mistake
Date: Sun, 14 Jun 2020 14:32:46 +0100 [thread overview]
Message-ID: <20200614143246.42b4f1d5@archlinux> (raw)
In-Reply-To: <20200609162943.867-1-f.suligoi@asem.it>
On Tue, 9 Jun 2020 18:29:43 +0200
Flavio Suligoi <f.suligoi@asem.it> wrote:
> Fix typo: "tigger" --> "trigger"
>
> Signed-off-by: Flavio Suligoi <f.suligoi@asem.it>
Sorry, was reading my email backwards and picked up same
fix from Keyur Patel.
Thanks though,
Jonathan
> ---
> drivers/iio/common/cros_ec_sensors/cros_ec_sensors_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/common/cros_ec_sensors/cros_ec_sensors_core.c b/drivers/iio/common/cros_ec_sensors/cros_ec_sensors_core.c
> index c831915ca7e5..4888fb23d801 100644
> --- a/drivers/iio/common/cros_ec_sensors/cros_ec_sensors_core.c
> +++ b/drivers/iio/common/cros_ec_sensors/cros_ec_sensors_core.c
> @@ -352,7 +352,7 @@ int cros_ec_sensors_core_init(struct platform_device *pdev,
> } else {
> /*
> * The only way to get samples in buffer is to set a
> - * software tigger (systrig, hrtimer).
> + * software trigger (systrig, hrtimer).
> */
> ret = devm_iio_triggered_buffer_setup(
> dev, indio_dev, NULL, trigger_capture,
prev parent reply other threads:[~2020-06-14 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 16:29 [PATCH 1/1] iio: common: fix spelling mistake Flavio Suligoi
2020-06-14 13:32 ` 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=20200614143246.42b4f1d5@archlinux \
--to=jic23@kernel.org \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=f.suligoi@asem.it \
--cc=fabien.lahoudere@collabora.com \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=sre@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