RTEMS | cpukit/libblock: memory cleanup and name generation failure(nvdisk) (!906)

[Joel Sherrill (@joel)]

Joel Sherrill commented on a discussion on cpukit/libblock/src/nvdisk.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/906#note_139942

 >  #define rtems_nvdisk_calc_crc16(_b, _c) \
 >    rtems_nvdisk_crc16_factor[((_b) ^ ((_c) & 0xff)) & 0xff] ^ (((_c) >> 8) & 0xff)
 >  
 > +/**
 > + * this describes the current state of mutext initialisation
 > + * whether the mutext on the current stage is initialised or not
 > + */
 > +typedef enum
 > +{
 > +    MUTEX_NOT_INITIALIZED = 0,
 > +    MUTEX_INITIALIZED
 > +} rtems_mutex_state_t;

I think I commented on the other thread that a bool would suffice and that anything starting with rtems_ is assumed to be public.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/906#note_139942
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/20260124/f4a9c55f/attachment.htm>