RTEMS | Reformat cpukit rtems src (!237)

[Amar Takhar (@amar)]

Amar Takhar commented on a discussion on cpukit/rtems/src/rtemsobjectgetapiclassname.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112449

 > -  { "Period",                  OBJECTS_RTEMS_PERIODS, 0},
 > -  { "Extension",               OBJECTS_RTEMS_EXTENSIONS, 0},
 > -  { "Barrier",                 OBJECTS_RTEMS_BARRIERS, 0},
 > -  { NULL,                      0, 0}
 > +  { "Task", OBJECTS_RTEMS_TASKS, 0 },
 > +  { "Timer", OBJECTS_RTEMS_TIMERS, 0 },
 > +  { "Semaphore", OBJECTS_RTEMS_SEMAPHORES, 0 },
 > +  { "Message Queue", OBJECTS_RTEMS_MESSAGE_QUEUES, 0 },
 > +  { "Partition", OBJECTS_RTEMS_PARTITIONS, 0 },
 > +  { "Region", OBJECTS_RTEMS_REGIONS, 0 },
 > +  { "Port", OBJECTS_RTEMS_PORTS, 0 },
 > +  { "Period", OBJECTS_RTEMS_PERIODS, 0 },
 > +  { "Extension", OBJECTS_RTEMS_EXTENSIONS, 0 },
 > +  { "Barrier", OBJECTS_RTEMS_BARRIERS, 0 },
 > +  { NULL, 0, 0 }
 >  };

@sebhub that's a good point thanks.  I'd still be OK with trying it and see what happens if we do end up triggering a lot of spurious changes we can disable it but at least if the first pass is good we can leave that in.  But arguably if it's triggering other changes wouldn't those be ones that should be done by hand, anyway?  It's not a big deal to disable it if it doesn't work out.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/237#note_112449
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/20240923/b73fb7ce/attachment.htm>