From: Nish Aravamudan <nish.aravamudan@canonical.com>
To: Nicholas Mc Guire <hofrat@osadl.org>
Cc: Corey Minyard <minyard@acm.org>,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Openipmi-developer] [PATCH] ipmi: pass timeout as HZ independent value
Date: Thu, 7 Jan 2016 07:37:29 -0800 [thread overview]
Message-ID: <20160107153729.GA19585@pitfall> (raw)
In-Reply-To: <1452174757-32188-1-git-send-email-hofrat@osadl.org>
On 07.01.2016 [14:52:37 +0100], Nicholas Mc Guire wrote:
> schedule_timeout_* takes a timeout in jiffies but the code currently is
> passing in a constant which makes this timeout HZ dependent, so pass it
> through msecs_to_jiffies() to fix this up.
>
> Signed-off-by: Nicholas Mc Guire <hofrat@osadl.org>
> ---
> patch was compile tested with x86_64_defconfig + CONFIG_IPMI_HANDLER=m
>
> Patch is against 4.4-rc8 (localversion-next is -next-20160107)
>
> drivers/char/ipmi/ipmi_si_intf.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/char/ipmi/ipmi_si_intf.c b/drivers/char/ipmi/ipmi_si_intf.c
> index 9fda22e..251d546 100644
> --- a/drivers/char/ipmi/ipmi_si_intf.c
> +++ b/drivers/char/ipmi/ipmi_si_intf.c
> @@ -1099,7 +1099,8 @@ static int ipmi_thread(void *data)
> schedule();
> else if (smi_result == SI_SM_IDLE) {
> if (atomic_read(&smi_info->need_watch)) {
> - schedule_timeout_interruptible(100);
> + schedule_timeout_interruptible(
> + msecs_to_jiffies(100));
I believe you can use msleep_interruptible() for this.
-Nish
next prev parent reply other threads:[~2016-01-07 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 13:52 [PATCH] ipmi: pass timeout as HZ independent value Nicholas Mc Guire
2016-01-07 15:37 ` Nish Aravamudan [this message]
2016-01-07 15:59 ` [Openipmi-developer] " Nicholas Mc Guire
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=20160107153729.GA19585@pitfall \
--to=nish.aravamudan@canonical.com \
--cc=hofrat@osadl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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