Just formatting, but Sebastian works in this area right now, so maybe
he can pluck it or ACK a push is ok.

I noticed it while reviewing his doc generation patches.

On Thu, Apr 22, 2021 at 9:12 AM Joel Sherrill <j...@rtems.org> wrote:
>
> If that's just a formatting error fix, looks good. Push it.
>
> If it's more, poke me.
>
> On Thu, Apr 22, 2021, 10:10 AM Gedare Bloom <ged...@rtems.org> wrote:
>>
>> ---
>>  c-user/rate-monotonic/background.rst | 4 +++-
>>  1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/c-user/rate-monotonic/background.rst 
>> b/c-user/rate-monotonic/background.rst
>> index 9ca7dff..c81af4e 100644
>> --- a/c-user/rate-monotonic/background.rst
>> +++ b/c-user/rate-monotonic/background.rst
>> @@ -112,7 +112,9 @@ less than its period.  For example, a periodic task's 
>> requirements may state
>>  that it should execute for 10 milliseconds every 100 milliseconds.  Although
>>  the execution time may be the average, worst, or best case, the worst-case
>>  execution time is more appropriate for use when analyzing system behavior 
>> under
>> -transient overload conditions... index:: aperiodic task, definition
>> +transient overload conditions.
>> +
>> +.. index:: aperiodic task, definition
>>
>>  In contrast, an aperiodic task executes at irregular intervals and has only 
>> a
>>  soft deadline.  In other words, the deadlines for aperiodic tasks are not
>> --
>> 2.25.1
>>
>> _______________________________________________
>> devel mailing list
>> devel@rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to