public inbox for newlib-cvs@sourceware.org help / color / mirror / Atom feed
From: Joel Sherrill <joel@sourceware.org> To: newlib-cvs@sourceware.org Subject: [newlib-cygwin] Correct prototypes of pthread_mutex_getprioceiling() and pthread_setschedparam() Date: Thu, 15 Mar 2018 14:26:00 -0000 [thread overview] Message-ID: <20180315142605.13419.qmail@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=948db3e4b7772d37f1eeeb28484282a435fdb30c commit 948db3e4b7772d37f1eeeb28484282a435fdb30c Author: Joel Sherrill <joel@rtems.org> Date: Wed Mar 14 17:49:29 2018 -0500 Correct prototypes of pthread_mutex_getprioceiling() and pthread_setschedparam() Diff: --- newlib/libc/include/pthread.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/newlib/libc/include/pthread.h b/newlib/libc/include/pthread.h index 3dee1c9..c9d24d6 100644 --- a/newlib/libc/include/pthread.h +++ b/newlib/libc/include/pthread.h @@ -156,7 +156,7 @@ int pthread_attr_getschedparam (const pthread_attr_t *__attr, int pthread_getschedparam (pthread_t __pthread, int *__policy, struct sched_param *__param); int pthread_setschedparam (pthread_t __pthread, int __policy, - struct sched_param *__param); + const struct sched_param *__param); /* Set Scheduling Priority of a Thread */ int pthread_setschedprio (pthread_t thread, int prio); @@ -190,7 +190,7 @@ int pthread_mutexattr_getprioceiling (const pthread_mutexattr_t *__attr, int pthread_mutex_setprioceiling (pthread_mutex_t *__mutex, int __prioceiling, int *__old_ceiling); -int pthread_mutex_getprioceiling (pthread_mutex_t *__mutex, +int pthread_mutex_getprioceiling (const pthread_mutex_t *__restrict __mutex, int *__prioceiling); #endif /* _POSIX_THREAD_PRIO_PROTECT */
reply other threads:[~2018-03-15 14:26 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180315142605.13419.qmail@sourceware.org \ --to=joel@sourceware.org \ --cc=newlib-cvs@sourceware.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).