From: Jonathan Cameron <jic23@kernel.org>
To: 赵西超 <zhao.xichao@vivo.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
"o.rempel@pengutronix.de" <o.rempel@pengutronix.de>,
"dlechner@baylibre.com" <dlechner@baylibre.com>,
"nuno.sa@analog.com" <nuno.sa@analog.com>,
"andy@kernel.org" <andy@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iio: adc: ti-tsc2046: use us_to_ktime() where appropriate
Date: Sat, 16 Aug 2025 14:08:09 +0100 [thread overview]
Message-ID: <20250816140809.2121a864@jic23-huawei> (raw)
In-Reply-To: <92f45b4d-447e-45ea-8fc0-a003a32d934c@vivo.com>
On Wed, 13 Aug 2025 11:33:24 +0000
赵西超 <zhao.xichao@vivo.com> wrote:
> 在 2025/8/13 18:34, Andy Shevchenko 写道:
>
> On Wed, Aug 13, 2025 at 9:56 AM Xichao Zhao <zhao.xichao@vivo.com><mailto:zhao.xichao@vivo.com> wrote:
>
>
>
> The scan_interval_us and time_per_scan_us are more suitable for
> using the us_to_ktime(). This can make the code more concise and
>
>
>
> This makes....
>
>
>
> enhance readability. Therefore, replace ns_to_ktime() with us_to_ktime().
>
>
>
> Perhaps Jonathan may tweak the commit message to be more English, but
> code wise I agree with you.
> Reviewed-by: Andy Shevchenko <andy@kernel.org><mailto:andy@kernel.org>
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
> Okay, thank you!
>
> Best regards,
>
> Xichao Zhao
>
Tweaked description and applied. Thanks for a nice cleanup.
Jonathan
prev parent reply other threads:[~2025-08-16 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 7:55 Xichao Zhao
2025-08-13 10:34 ` Andy Shevchenko
[not found] ` <92f45b4d-447e-45ea-8fc0-a003a32d934c@vivo.com>
2025-08-16 13:08 ` 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=20250816140809.2121a864@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=o.rempel@pengutronix.de \
--cc=zhao.xichao@vivo.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
all inboxes | Powered by JetHome®