RTEMS | cpukit: Add msg broadcast non-atomicity to doc (!810)

[Martin Werner (@martinerikwerner)]

Martin Werner created a merge request: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/810

Project:Branches: martinerikwerner/rtems:msg-broadcast-is-non-atomic to rtems/rtos/rtems:main
Author:   Martin Werner




## Summary

cpukit: Add msg broadcast non-atomicity to doc

rtems_message_queue_broadcast() may, under certain circumstances, copy
the message to tasks which were not waiting on the message queue when
the broadcast started, and may copy the message multiple times to the
same task.

This behaviour is, based on discussion in #4804, something that might
not chane in the short term, so expose it in the user documentation.

The wording is copied with modifications from an existing internal
requirements note.

Also correct "none-atomic" -> "non-atomic" in said internal requirements
note.

The changes were auto-generated from rtems-central.


<!-- Default settings, if it is a dropdown it will set after submission -->

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/810
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20251018/624a1cd6/attachment.htm>