[RTEMS Project] #4669: clock_nanosleep() uses the wrong clock to determine the start time point

[RTEMS trac]

#4669: clock_nanosleep() uses the wrong clock to determine the start time point
-----------------------------+------------------------------
 Reporter:  Sebastian Huber  |       Owner:  Sebastian Huber
     Type:  defect           |      Status:  closed
 Priority:  normal           |   Milestone:  6.1
Component:  score            |     Version:  5
 Severity:  normal           |  Resolution:  fixed
 Keywords:                   |  Blocked By:
 Blocking:                   |
-----------------------------+------------------------------
Changes (by Sebastian Huber <sebastian.huber@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"cd50bea678baa494640415377f7be146246ba3e4/rtems"
 cd50bea/rtems]:
 {{{
 #!CommitTicketReference repository="rtems"
 revision="cd50bea678baa494640415377f7be146246ba3e4"
 score: Use right clock for threadq timeouts

 Use CLOCK_REALTIME and CLOCK_MONOTONIC for relative thread queue timeouts
 instead of CLOCK_REALTIME_COARSE and CLOCK_MONOTONIC_COARSE.  This fixes
 an
 issue with clock_nanosleep() in combination with clock_gettime().

 Close #4669.
 }}}

--
Ticket URL: <http://devel.rtems.org/ticket/4669#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project