From 03d7cb9f9eea8279f3b39b8666411a861cfe6c69 Mon Sep 17 00:00:00 2001 From: Giovanni Di Sirio Date: Mon, 7 Oct 2019 15:21:57 +0000 Subject: [PATCH] Documentation fixes. git-svn-id: svn://svn.code.sf.net/p/chibios/svn/trunk@13094 27425a3e-05d8-49a3-a47f-9c15f0e5edd8 --- os/rt/src/chevents.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/os/rt/src/chevents.c b/os/rt/src/chevents.c index d86847c0e..5729e5176 100644 --- a/os/rt/src/chevents.c +++ b/os/rt/src/chevents.c @@ -31,12 +31,12 @@ * @p thread_t structure. * Operations defined for events: * - Wait, the invoking thread goes to sleep until a certain - * AND/OR combination of events become pending. + * AND/OR combination of events are signaled. * - Clear, a mask of events is cleared from the pending * events, the cleared events mask is returned (only the * events that were actually pending and then cleared). - * - Signal, an events mask is directly ORed to the mask of the - * signaled thread. + * - Signal, an events mask is directly ORed to the mask of + * the signaled thread. * - Broadcast, each thread registered on an Event Source is * signaled with the events specified in its Event Listener. * - Dispatch, an events mask is scanned and for each bit set @@ -50,8 +50,8 @@ * An unlimited number of Event Sources can exists in a system and * each thread can be listening on an unlimited number of * them. - * @pre In order to use the Events APIs the @p CH_CFG_USE_EVENTS option must be - * enabled in @p chconf.h. + * @pre In order to use the Events APIs the @p CH_CFG_USE_EVENTS option + * must be enabled in @p chconf.h. * @post Enabling events requires 1-4 (depending on the architecture) * extra bytes in the @p thread_t structure. * @{