NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/59127 (clock_getres(2) returns EINVAL for CLOCK_{PROCESS,THREAD}_CPUTIME_ID)

To: kern-bug-people%netbsd.org@localhost,netbsd-bugs%netbsd.org@localhost,gnats-admin%netbsd.org@localhost,riastradh%NetBSD.org@localhost,pho%cielonegro.org@localhost
Subject: Re: kern/59127 (clock_getres(2) returns EINVAL for CLOCK_{PROCESS,THREAD}_CPUTIME_ID)
From: riastradh%NetBSD.org@localhost
Date: Tue, 25 Mar 2025 19:49:38 +0000 (UTC)

Synopsis: clock_getres(2) returns EINVAL for CLOCK_{PROCESS,THREAD}_CPUTIME_ID

State-Changed-From-To: closed->needs-pullups
State-Changed-By: riastradh%NetBSD.org@localhost
State-Changed-When: Tue, 25 Mar 2025 19:49:38 +0000
State-Changed-Why:
Does this need pullup-9, pullup-10?

Follow-Ups:
- Re: kern/59127 (clock_getres(2) returns EINVAL for CLOCK_{PROCESS,THREAD}_CPUTIME_ID)
  - From: PHO

Prev by Date: port-xen/59212: XEN3_DOM0 panics as NR_PIRQS is too small
Next by Date: Re: kern/59127 (clock_getres(2) returns EINVAL for CLOCK_{PROCESS,THREAD}_CPUTIME_ID)
Previous by Thread: Re: kern/59127 (clock_getres(2) returns EINVAL for CLOCK_{PROCESS,THREAD}_CPUTIME_ID)
Next by Thread: Re: kern/59127 (clock_getres(2) returns EINVAL for CLOCK_{PROCESS,THREAD}_CPUTIME_ID)
Indexes:

Home | Main Index | Thread Index | Old Index