This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: How to use sem_timedwait with CLOCK_MONOTONIC?
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: Alexandre Bique <bique dot alexandre at gmail dot com>
- Cc: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>, "libc-help at sourceware dot org" <libc-help at sourceware dot org>
- Date: Thu, 16 Feb 2017 08:15:29 -0500
- Subject: Re: How to use sem_timedwait with CLOCK_MONOTONIC?
- Authentication-results: sourceware.org; auth=none
- References: <CAP737oKgdEw08Wzeb-weB9c7=Gzh7fDdG0V2NKU81s_WAUcUAA@mail.gmail.com> <67fed762-bb8c-3038-ee34-337bf0176b29@linaro.org> <CAP737oKndR-gQG0yuUKTZ_h62S8tF8AOHt0Jh7a3bk4tgeen_w@mail.gmail.com>
On Thu, Feb 16, 2017 at 7:41 AM, Alexandre Bique
<bique.alexandre@gmail.com> wrote:
> If I provide a patch which implements sem_timedwait_np(sem, timeout,
> clock), is there any chances that it gets merged for the next release?
Alexandre,
A patch is part of the process, it also needs documentation, and a
regression test.
There is also some work to be done to integrate feedback and reviews
of the patches to get them to a point where the API is acceptable to
the senior developers who maintain the project. In this case the API
design seems pretty straight forward.
The contribution checklist is here which covers the nit-picky details
of the actual submission:
https://sourceware.org/glibc/wiki/Contribution%20checklist
FSF Copyright assignment is something you would want to start early to
get your patch accepted.
Cheers,
Carlos.