From: Kushal-kothari <kushalkothari285@gmail.com>
To: linux-arm-kernel@lists.infradead.org, mike.rapoport@gmail.com,
kushalkothari2850@gmail.com, kushalkothari285@gmail.com,
outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
nsaenz@kernel.org, bcm-kernel-feedback-list@broadcom.com
Subject: [PATCH v2] staging: vc04_services: replace msleep() by usleep_range()
Date: Sun, 17 Oct 2021 14:59:00 +0530 [thread overview]
Message-ID: <20211017092900.134752-1-kushalkothari285@gmail.com> (raw)
Fixed the warning:-msleep < 20ms can sleep for up to 20ms by replacing
msleep(unsigned long msecs) by usleep_range(unsigned long min, unsigned long max)
in usecs as msleep(1ms~20ms) can sleep for upto 20 ms.
Signed-off-by: Kushal-kothari <kushalkothari285@gmail.com>
---
Changes from v1: Reword both the subject and the log message.
drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c
index 6fbafdfe340f..80a7898c5331 100644
--- a/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c
+++ b/drivers/staging/vc04_services/interface/vchiq_arm/vchiq_arm.c
@@ -857,7 +857,7 @@ vchiq_bulk_transmit(unsigned int handle, const void *data, unsigned int size,
if (status != VCHIQ_RETRY)
break;
- msleep(1);
+ usleep_range(1000, 2000);
}
return status;
@@ -894,7 +894,7 @@ enum vchiq_status vchiq_bulk_receive(unsigned int handle, void *data,
if (status != VCHIQ_RETRY)
break;
- msleep(1);
+ usleep_range(1000, 2000);
}
return status;
--
2.25.1
next reply other threads:[~2021-10-17 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 9:29 Kushal-kothari [this message]
2021-10-17 9:37 ` [PATCH v2] staging: vc04_services: replace msleep() by usleep_range() Greg KH
2021-10-17 9:52 ` [Outreachy kernel] " Julia Lawall
2021-10-17 11:56 ` Stefan Wahren
2021-10-17 12:33 ` Julia Lawall
2021-10-17 12:47 ` Stefan Wahren
2021-11-03 10:48 ` Dan Carpenter
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=20211017092900.134752-1-kushalkothari285@gmail.com \
--to=kushalkothari285@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=kushalkothari2850@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mike.rapoport@gmail.com \
--cc=nsaenz@kernel.org \
--cc=outreachy-kernel@googlegroups.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