From: Jonathan Cameron <jic23@kernel.org>
To: Andy Shen Shen <shengaoya@inspur.com>
Cc: <lars@metafoo.de>, <robh@kernel.org>, <linux-iio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iio: adc: for kernel comment
Date: Sat, 23 Sep 2023 18:39:49 +0100 [thread overview]
Message-ID: <20230923183949.62b9715b@jic23-huawei> (raw)
In-Reply-To: <20230921031444.63594-1-shengaoya@inspur.com>
On Thu, 21 Sep 2023 11:14:44 +0800
Andy Shen Shen <shengaoya@inspur.com> wrote:
> In line 460 of the palmas_gpadc.c file, fix kernel comment errors.
For future reference (I've tweaked it this time) please include
the driver name in the description and also say what the change
was at least briefly (drop duplicated the).
Applied to the togreg branch of iio.git and pushed out as testing because
other things on that branch need some build testing etc.
Thanks,
Jonathan
>
> Signed-off-by: Andy Shen Shen <shengaoya@inspur.com>
> ---
> 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 e202ea18af10..203cbbc70719 100644
> --- a/drivers/iio/adc/palmas_gpadc.c
> +++ b/drivers/iio/adc/palmas_gpadc.c
> @@ -457,7 +457,7 @@ static int palmas_gpadc_get_calibrated_code(struct palmas_gpadc *adc,
> *
> * 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 the channel is calibrated (trimmed) or not.
> + * the channel is calibrated (trimmed) or not.
> */
> static int palmas_gpadc_threshold_with_tolerance(int val, const int INL,
> const int gain_error,
prev parent reply other threads:[~2023-09-23 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 3:14 [PATCH] iio: adc: for kernel comment Andy Shen Shen
2023-09-23 17:39 ` 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=20230923183949.62b9715b@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shengaoya@inspur.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;
as well as URLs for NNTP newsgroup(s).