Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'LDT-2990-iofp-fw-and-fpga-version' into develop

LDT-2990: added fp version response to the dd handle version request message.

Please change bloodLeakState != BLOOD_LEAK_VERIFY_INTENSITY_AFTER_ZEROING_STATE to BLOOD_LEAK_VERIFY_INTENSITY_AFTER_ZEROING_STATE != bloodLeakState

Please change

bloodLeakState != BLOOD_LEAK_VERIFY_INTENSITY_AFTER_ZEROING_STATE
to
BLOOD_LEAK_VERIFY_INTENSITY_AFTER_ZEROING_STATE != bloodLeakState

Please remove extra line

Please remove extra line

Minor: Need space in (BLOOD_LEAK_EMB_MODE_CMD_T)

Minor: Need space in (BLOOD_LEAK_EMB_MODE_CMD_T)

Minor: Need space between parentheses

Minor: Need space between parentheses

Minor: Need space between parentheses

Minor: Need space between parentheses

Merge branch 'staging' into LDT-2004-v2-conductivity-sensors

Remove the empty space.

Remove the empty space.

Can we remove this #if check? we can keep the comment.

Can we remove this #if check? we can keep the comment.

Bamboo Commit: Updated DDCommon.h with build versions from Bamboo.

can we get each group of level check in to a function and call those functions for each case?

can we get each group of level check in to a function and call those functions for each case?

Minor: Please add space in [cmd].

Minor: Please add space in [cmd].

Should it be bloodLeakEmbModeCmd?

Should it be bloodLeakEmbModeCmd?

Bamboo Commit: Updated DDCommon.h with build versions from Bamboo.

LDT-3344 merged into develop

Bamboo Commit: Updated DDCommon.h with build versions from Bamboo.

LDT-3344 added get functions for newly implemented sensors

Bamboo Commit: Updated DDCommon.h with build versions from Bamboo.

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

changed.

changed.

Add a comment to right listing math functions used.

Add a comment to right listing math functions used.

Remove blank line.

Remove blank line.

Can you follow up with whoever commented it out and find out if that was intentional? And, if so, will it be coming back? And, if so, should we at least put a TODO on this to restore later?

Can you follow up with whoever commented it out and find out if that was intentional? And, if so, will it be coming back? And, if so, should we at least put a TODO on this to restore later?

Why not "TRUE == "?

Why not "TRUE == "?