Ivy Zhuang commented on a discussion on cpukit/include/rtems/score/mpcpimpl.h: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1358#note_155062 > +/** > + * @brief Releases according to MPCP. > + * > + * @param mpcp The MPCP control for the operation. > + * @param queue_context The thread queue context. > + */ > +static inline void _MPCP_Release( > + MPCP_Control *mpcp, > + Thread_queue_Context *queue_context > +) > +{ > + _Thread_queue_Release( &mpcp->Wait_queue, queue_context ); > +} > + > +/** > + * @brief Gets owner of the MPCP control. Conceptually, it's the owner of the lock that uses MPCP which is also the owner of the MPCP wait queue. I see what you mean though, the wording could be more clear. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1358#note_155062 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/sent_notifications/4-eshwoldht2mmqrka3wj0ni8ys-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
