From: Jonathan Cameron <jic23@kernel.org>
To: Kuldeep Pisda <pisdak79@gmail.com>
Cc: lars@metafoo.de, linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: adc: palmas: Fix typo in threshold calculation comment
Date: Sun, 1 Dec 2024 12:58:07 +0000 [thread overview]
Message-ID: <20241201125807.2b3ea19a@jic23-huawei> (raw)
In-Reply-To: <20241123112757.63928-1-pisdak79@gmail.com>
On Sat, 23 Nov 2024 11:27:57 +0000
Kuldeep Pisda <pisdak79@gmail.com> wrote:
> Fix a typo in the GPADC threshold calculation documentation where
> "paramenters" was incorrectly written instead of "parameters".
>
> Signed-off-by: Kuldeep Pisda <pisdak79@gmail.com>
Hi. I already have a patch queued that fixes this up.
Thanks,
Jonathan
> ---
> drivers/iio/adc/palmas_gpadc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/adc/palmas_gpadc.c b/drivers/iio/adc/palmas_gpadc.c
> index 203cbbc70719..67d567ee21b4 100644
> --- a/drivers/iio/adc/palmas_gpadc.c
> +++ b/drivers/iio/adc/palmas_gpadc.c
> @@ -456,7 +456,7 @@ static int palmas_gpadc_get_calibrated_code(struct palmas_gpadc *adc,
> * raw high threshold = (ideal threshold + INL) * gain error + offset error
> *
> * The gain error include both gain error, as specified in the datasheet, and
> - * the gain error drift. These paramenters vary depending on device and whether
> + * the gain error drift. These parameters vary depending on device and whether
> * the channel is calibrated (trimmed) or not.
> */
> static int palmas_gpadc_threshold_with_tolerance(int val, const int INL,
prev parent reply other threads:[~2024-12-01 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 11:27 [PATCH] iio: adc: palmas: Fix typo in threshold calculation comment Kuldeep Pisda
2024-12-01 12:58 ` 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=20241201125807.2b3ea19a@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pisdak79@gmail.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