linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] Completion API extension
Date: Fri, 22 Oct 2004 08:45:29 +0200	[thread overview]
Message-ID: <1098427528.8955.45.camel@thomas> (raw)
In-Reply-To: <200410212118.32981.dtor_core@ameritech.net>

On Fri, 2004-10-22 at 04:18, Dmitry Torokhov wrote:

Hi,

it's resubmitted in a correct version already.

Thanks,

tglx


> Hi,
> 
> On Wednesday 20 October 2004 11:31 am, Thomas Gleixner wrote:
> > +unsigned long fastcall __sched
> > +wait_for_completion_interruptible_timeout(struct completion *x,
> > +                                         unsigned long timeout)
> > +{
> > +       might_sleep();
> > +
> > +       spin_lock_irq(&x->wait.lock);
> > +       if (!x->done) {
> > +               DECLARE_WAITQUEUE(wait, current);
> > +
> > +               wait.flags |= WQ_FLAG_EXCLUSIVE;
> > +               __add_wait_queue_tail(&x->wait, &wait);
> > +               do {
> > +                       if (signal_pending(current)) {
> > +                               timeout = -ERESTARTSYS;
> > +                               goto out;
> > +                       }
> > +                       __set_current_state(TASK_INTERRUPTIBLE);
> > +                       spin_unlock_irq(&x->wait.lock);
> > +                       schedule();
> 
> 			^^^^^^^^^^^^^^^^^^
> 
> schedule_timeout perhaps?
> 


      parent reply	other threads:[~2004-10-22  7:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20 16:31 [PATCH] Completion API extension Thomas Gleixner
2004-10-21 20:49 ` Thomas Gleixner
     [not found] ` <200410212118.32981.dtor_core@ameritech.net>
2004-10-22  6:45   ` Thomas Gleixner [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=1098427528.8955.45.camel@thomas \
    --to=tglx@linutronix.de \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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).