Gedare Bloom commented on a discussion on cpukit/include/rtems/rtems/event.h: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/444#note_121311 > /** > * @brief This event set constant represents the reserved system event that > is > * internally used by aio_suspend to notify of suspension termination. > - * > - * @par Constraints > - * @parblock > - * The following constraints apply to this constant: > - * > - * * The constant is not included in the pre-qualified feature set of RTEMS. > - * Applications which are restricted to only use interfaces of the > - * pre-qualified feature set of RTEMS shall not use the constant. > - * @endparblock > */ "How does https://gitlab.rtems.org/rtems/prequal/rtems-central/-/merge_requests/5 relate?" That is the pending MR that adds the specification of the AIO Event. As you rightly pointed out, we don't have a proper way yet of managing these relationships between `rtems-central` and `rtems`. It would be great to sort it out. The AIO Suspension was merged in !275 with some content that was generated from `rtems-central` based on the rtems/prequal/rtems-central!5 but this content was not correct, because at that time `rtems-central` was still pointing to a developer's personal `rtems.git` and not to the upstream `rtems.git`. Now that we got the relationship between `rtems-central.git` and `rtems.git` a little more straight in rtems/prequal/rtems-central!2 we are getting closer to being able to figure out the right way to keep these repositories working together. Meanwhile, this MR is about removing the added content that was generated with the slightly broken version of `rtems-central` from before rtems/prequal/rtems-central!2 I hope I got that a bit more straight. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/444#note_121311 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
