SHIVAM DEOLANKAR commented on a discussion on testsuites/validation/tc-intr-set-priority.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1254#note_150812 > } > > sc = rtems_interrupt_set_priority( vector, priority ); > + > + /* > + * Some BSPs support full uint32_t priority range > + * UINT32_MAX may be valid. > + */ > + if ( !ctx->valid_priority && sc == RTEMS_SUCCESSFUL ){ My intention here was to preserve validation on BSPs where full range of uint32_t is still valid. Should we introduce BSP defined bounds or dynamically adapt the expected status of validation? -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1254#note_150812 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
