All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: "b.gunreben" <b.gunreben@web.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] nanosleep
Date: Sat, 9 Nov 2002 14:26:52 -0500	[thread overview]
Message-ID: <20021109192651.GC15380@systemhalted> (raw)
In-Reply-To: <3DCCC839.EFC91019@web.de>

> > glibc 2.3.1 from debian CVS or upstream?
> 
> This is upstream with hppa patches from the debian tree. 

That's currently broke, and I've been slotting in my time to fix this.
Currently rebuilding glibc :}
 
> The report was probably bad. In the mail thread I mentioned in my
> previous mail, the nanosleep in the kernel was fixed because of
> threading problems. If I understand it correctly, threading will always
> have problems without a realy working nanosleep.
 
Yes. You'll see it's use sprinkled in linuxthreads/* and in particular 
spinlock.c

c.

      reply	other threads:[~2002-11-09 19:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-08 11:16 [parisc-linux] nanosleep Berthold Gunreben
2002-11-08 16:12 ` Carlos O'Donell
2002-11-09  8:32   ` b.gunreben
2002-11-09 19:26     ` Carlos O'Donell [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=20021109192651.GC15380@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=b.gunreben@web.de \
    --cc=parisc-linux@lists.parisc-linux.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.