Re: kern/50295 (clock_nanosleep(2) sets errno instead of returning error)

To: kern-bug-people%netbsd.org@localhost,netbsd-bugs%netbsd.org@localhost,gnats-admin%netbsd.org@localhost,dholland%NetBSD.org@localhost,christos%NetBSD.org@localhost
Subject: Re: kern/50295 (clock_nanosleep(2) sets errno instead of returning error)
From: dholland%NetBSD.org@localhost
Date: Sun, 1 May 2016 05:27:02 +0000 (UTC)

Synopsis: clock_nanosleep(2) sets errno instead of returning error

State-Changed-From-To: feedback->closed
State-Changed-By: dholland%NetBSD.org@localhost
State-Changed-When: Sun, 01 May 2016 05:27:02 +0000
State-Changed-Why:
Feedback timeout.

much as errno sucks, functions that arbitrarily return error codes instead
are a blight.

Prev by Date: Re: kern/9444 (netbsd doesn't send gratuitious arps when an interface comes up)
Next by Date: Re: kern/41082 (destroying a locked vlockmgr lock on shutdown)
Previous by Thread: Re: kern/50295 (clock_nanosleep(2) sets errno instead of returning error)
Next by Thread: kern/50296: gpio driver is marked MPSAFE but is not
Indexes:

Home | Main Index | Thread Index | Old Index