AlarmMgmtTD.c

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
mesage payload is not an input. We correctly mentioned it in the param. Input should be none as we are not reading any global or static variable declared at file level.

mesage payload is not an input. We correctly mentioned it in the param.
Input should be none as we are not reading any global or static variable declared at file level.

Output should be none as we are not updating any global or static variable declared at file level.

Output should be none as we are not updating any global or static variable declared at file level.

Please convert the function to have only single point of return. You can assign result = FALSE here. Also check for whitespace characters. Use 4 spaces instead of tab.

Please convert the function to have only single point of return.
You can assign result = FALSE here.

Also check for whitespace characters. Use 4 spaces instead of tab.

Add space : Change all sizeof(ALARM_ID_T) to sizeof( ALARM_ID_T )

Add space : Change all sizeof(ALARM_ID_T) to sizeof( ALARM_ID_T )

Why are we adding this header here?

Why are we adding this header here?

Added

Added

LEAHI-TD-FIRMWARE-LDT-4160_[Request] Get function for full detailed Alarm Table
LEAHI-TD-FIRMWARE-LDT-4160_[Request] Get function for full detailed Alarm Table
LDT-4160- Added a new functaion to pull the alarm properties

  1. … 2 more files in changeset.
Thank you for the clarification!

Thank you for the clarification!

break into two lines

break into two lines

Add alarm ALARM_ID_TD_EMPTY_SALINE_BAG

Add alarm ALARM_ID_TD_EMPTY_SALINE_BAG

Add newAlarmIndicateStop to output

Add newAlarmIndicateStop to output

Add newAlarmIndicateStop to input and output.

Add newAlarmIndicateStop to input and output.

Arpita, we don't want to use doxygen style comments for function prototypes since we cover functions with the function headers. so this is the proper type of comments.

Arpita, we don't want to use doxygen style comments for function prototypes since we cover functions with the function headers. so this is the proper type of comments.

pauseBolusResumeState is input

pauseBolusResumeState is input

add alarm

add alarm

Replace // to ///< for line 56 to 60

Replace // to ///< for line 56 to 60

Use // comments for function prototypes.

Use // comments for function prototypes.

Either no comment or // comment for function prototypes since doxygen captures function details from function headers.

Either no comment or // comment for function prototypes since doxygen captures function details from function headers.

These were fine (and preferred) as // because doxygen gets function details from function headers in the .c file.

These were fine (and preferred) as // because doxygen gets function details from function headers in the .c file.

remove this

remove this

remove this case

remove this case

remove this

remove this

remove this

remove this

Fixed

Fixed

I fixed it but it is not showing in crucible

I fixed it but it is not showing in crucible

Fixed

Fixed

Fixed

Fixed