From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-kernel@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
Heiner Kallweit <hkallweit1@gmail.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [RFC PATCH 04/15] iio: adc: use new name 'usleep_autoyield' instead of 'fsleep'
Date: Mon, 21 Mar 2022 17:12:12 +0100 [thread overview]
Message-ID: <20220321161223.2837-5-wsa+renesas@sang-engineering.com> (raw)
In-Reply-To: <20220321161223.2837-1-wsa+renesas@sang-engineering.com>
The function was just renamed to be easier understandable. No functional
change.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
---
RFC, please do not apply yet
drivers/iio/adc/ti-tsc2046.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/adc/ti-tsc2046.c b/drivers/iio/adc/ti-tsc2046.c
index e8fc4d01f30b..d0d041ec632a 100644
--- a/drivers/iio/adc/ti-tsc2046.c
+++ b/drivers/iio/adc/ti-tsc2046.c
@@ -464,7 +464,7 @@ static void tsc2046_adc_reenable_trigger(struct iio_trigger *trig)
*/
delta = priv->scan_interval_us - priv->time_per_scan_us;
if (delta > 0)
- fsleep(delta);
+ usleep_autoyield(delta);
spin_lock_irqsave(&priv->trig_lock, flags);
--
2.34.1
next prev parent reply other threads:[~2022-03-21 16:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 16:12 [RFC PATCH 00/15] treewide: rename fsleep Wolfram Sang
2022-03-21 16:12 ` [RFC PATCH 01/15] delay: rename fsleep to usleep_autoyield Wolfram Sang
2022-03-21 16:12 ` [RFC PATCH 02/15] base: regmap: use new name 'usleep_autoyield' instead of 'fsleep' Wolfram Sang
2022-03-21 16:12 ` [RFC PATCH 03/15] bus: mhi: core: " Wolfram Sang
2022-03-21 16:12 ` Wolfram Sang [this message]
2022-03-21 16:12 ` [RFC PATCH 05/15] memory: tegra: " Wolfram Sang
2022-03-21 16:12 ` [RFC PATCH 06/15] mfd: " Wolfram Sang
2022-03-21 16:12 ` [RFC PATCH 07/15] mux: " Wolfram Sang
2022-03-21 16:12 ` [RFC PATCH 08/15] net: ethernet: realtek: " Wolfram Sang
2022-03-21 16:12 ` [RFC PATCH 09/15] net: mdio: " Wolfram Sang
2022-03-21 16:12 ` [RFC PATCH 10/15] net: phy: " Wolfram Sang
2022-03-21 16:12 ` [RFC PATCH 11/15] net: wireless: realtek: rtw88: " Wolfram Sang
2022-03-21 16:12 ` [RFC PATCH 12/15] net: wireless: realtek: rtw89: " Wolfram Sang
2022-03-21 16:12 ` [RFC PATCH 13/15] thermal: tegra: " Wolfram Sang
2022-03-21 16:12 ` [RFC PATCH 14/15] usb: chipidea: " Wolfram Sang
2022-03-21 16:12 ` [RFC PATCH 15/15] delay: remove the fallback for fsleep Wolfram Sang
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=20220321161223.2837-5-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.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).