From: Greg KH <greg@kroah.com>
To: kernel-janitors@vger.kernel.org
Subject: [Kernel-janitors] Re: [PATCH] pci/cpci_hotplug_core: replace
Date: Tue, 27 Jul 2004 22:10:59 +0000 [thread overview]
Message-ID: <20040727221059.GA21125@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0407271755360.26002@rancor.yyz.somanetworks.com>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
On Tue, Jul 27, 2004 at 06:04:19PM -0400, Scott Murray wrote:
> On Tue, 27 Jul 2004, Nishanth Aravamudan wrote:
>
> > I would appreciate any comments from the janitors list. This is one (of
> > many) cases where I made a decision about replacing
> >
> > set_current_state(TASK_INTERRUPTIBLE);
> > schedule_timeout(some_time);
> >
> > with
> >
> > msleep(jiffies_to_msecs(some_time));
> >
> > msleep() is not exactly the same as the previous code, but I only did
> > this replacement where I thought long delays were *desired*. If this is
> > not the case here, then just disregard this patch.
>
> msleep sets TASK_UNINTERRUPTIBLE and not TASK_INTERRUPTIBLE, which I think
> will work okay in this instance, but am not actually sure. I'm leaving
> for two weeks vacation tomorrow, so I'm not in a position to test this out
> at the moment. Greg, can you comment on the correctness of this?
Yes, this should be safe at this point in time. I'll apply the patch in
my next round of PCI patches.
thanks,
greg k-h
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2004-07-27 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 22:04 [Kernel-janitors] Re: [PATCH] pci/cpci_hotplug_core: replace Scott Murray
2004-07-27 22:10 ` Greg KH [this message]
2004-08-02 22:42 ` Greg KH
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=20040727221059.GA21125@kroah.com \
--to=greg@kroah.com \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.