What the developer wrote
Authored by Niklas Dusenlund
formatting
What changed, and why it matters
This commit only adds a single space after two type casts in the same C source file. It is a pure code-formatting change with no functional difference and no security relevance.
No action required; the change is cosmetic.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies two lines in src/qtouch/qtouch.c, changing (uint8_t)~(1U << ...) to (uint8_t) ~(1U << ...). This is a whitespace-only formatting adjustment. The C operator precedence and generated behavior are identical before and after the change.
Changed components
src/qtouch/qtouch.cInspect captured patch +2 / −2
diff --git a/src/qtouch/qtouch.c b/src/qtouch/qtouch.c
index ad146e0..f6ad8f5 100644
--- a/src/qtouch/qtouch.c
+++ b/src/qtouch/qtouch.c
@@ -462,7 +462,7 @@ void qtouch_process(void)
/* if the Acquistion request was successful then clear the request flag */
if (TOUCH_SUCCESS == touch_ret) {
/* Clear the Measure request flag */
- p_qtm_control->binding_layer_flags &= (uint8_t)~(1U << time_to_measure_touch);
+ p_qtm_control->binding_layer_flags &= (uint8_t) ~(1U << time_to_measure_touch);
}
}
@@ -481,7 +481,7 @@ void qtouch_process(void)
}
/* Reset the flags for node_level_post_processing */
- p_qtm_control->binding_layer_flags &= (uint8_t)~(1U << node_pp_request);
+ p_qtm_control->binding_layer_flags &= (uint8_t) ~(1U << node_pp_request);
if (p_qtm_control->binding_layer_flags & (1U << reburst_request)) {
p_qtm_control->binding_layer_flags |= (1U << time_to_measure_touch);
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.