drivers/can/can_mspm0g3xxx_canfd.c:104 trailing whitespace

drivers/can/can_mspm0g3xxx_canfd.c:118 trailing whitespace

soc/arm/ti_mspm0/mspm0g3xxx/soc.c:45 do not use C99 // comments

soc/arm/ti_mspm0/mspm0g3xxx/soc.c:48 trailing whitespace

soc/arm/ti_mspm0/mspm0g3xxx/soc.c:49 trailing whitespace

soc/arm/ti_mspm0/mspm0g3xxx/soc.c:50 trailing whitespace

soc/arm/ti_mspm0/mspm0g3xxx/soc.c:68 space required after that ',' (ctx:VxV)

soc/arm/ti_mspm0/mspm0g3xxx/soc.h:20 trailing whitespace

soc/arm/ti_mspm0/mspm0g3xxx/soc.h:21 trailing whitespace

soc/arm/ti_mspm0/mspm0g3xxx/soc.h:22 trailing whitespace

See https://docs.zephyrproject.org/latest/contribute/guidelines.html#coding-style for more details. TYPO_SPELLING: 'maping' may be misspelled - perhaps 'mapping'? File:arch/arm/core/cortex_a_r/smp.c Line:80 CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test File:drivers/can/can_mspm0g3xxx_canfd.c Line:77 CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test File:drivers/can/can_mspm0g3xxx_canfd.c Line:92 TRAILING_WHITESPACE: trailing whitespace File:drivers/can/can_mspm0g3xxx_canfd.c Line:104 CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test File:drivers/can/can_mspm0g3xxx_canfd.c Line:104 TRAILING_WHITESPACE: trailing whitespace File:drivers/can/can_mspm0g3xxx_canfd.c Line:118 TYPO_SPELLING: 'perfomance' may be misspelled - perhaps 'performance'? File:drivers/crypto/crypto_smartbond.c Line:386 TYPO_SPELLING: 'retrived' may be misspelled - perhaps 'retrieved'? File:drivers/dma/dma_smartbond.c Line:90 TYPO_SPELLING: 'perfomance' may be misspelled - perhaps 'performance'? File:drivers/dma/dma_smartbond.c Line:268 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:468 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:548 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:633 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:695 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:720 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:738 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:761 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:783 TYPO_SPELLING: 'Inavlid' may be misspelled - perhaps 'Invalid'? File:drivers/dma/dma_smartbond.c Line:869 TYPO_SPELLING: 'the the' may be misspelled - perhaps 'the'? File:drivers/serial/uart_intel_lw.c Line:71 TYPO_SPELLING: 'alredy' may be misspelled - perhaps 'already'? File:drivers/timer/cortex_m_systick.c Line:418 TYPO_SPELLING: 'INTERUPT' may be misspelled - perhaps 'INTERRUPT'? File:drivers/watchdog/wdt_xmc4xxx.c Line:37 TYPO_SPELLING: 'peripherial' may be misspelled - perhaps 'peripheral'? File:dts/bindings/dma/andestech,atcdmac300.yaml Line:32 TYPO_SPELLING: 'triggerd' may be misspelled - perhaps 'triggered'? File:dts/bindings/power-domain/power-domain-gpio-monitor.yaml Line:9 LINE_SPACING: Missing a blank line after declarations File:include/zephyr/input/input_kbd_matrix.h Line:119 TYPO_SPELLING: 'configuation' may be misspelled - perhaps 'configuration'? File:include/zephyr/net/ieee802154_radio.h Line:1054 UNNECESSARY_ELSE: else is not generally useful after a break or return File:lib/heap/heap_stress.c Line:48 MACRO_WITH_FLOW_CONTROL: Macros with flow control statements should be avoided File:lib/heap/heap_validate.c Line:21 FUNCTION_ARGUMENTS: function definition argument 'int' should also have an identifier name File:lib/libc/common/include/threads.h Line:55 CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test File:soc/arm/ti_mspm0/mspm0g3xxx/soc.c Line:27 LEADING_SPACE: please, no spaces at the start of a line File:soc/arm/ti_mspm0/mspm0g3xxx/soc.c Line:29 C99_COMMENTS: do not use C99 // comments File:soc/arm/ti_mspm0/mspm0g3xxx/soc.c Line:45 TRAILING_WHITESPACE: trailing whitespace File:soc/arm/ti_mspm0/mspm0g3xxx/soc.c Line:48 TRAILING_WHITESPACE: trailing whitespace File:soc/arm/ti_mspm0/mspm0g3xxx/soc.c Line:49 TRAILING_WHITESPACE: trailing whitespace File:soc/arm/ti_mspm0/mspm0g3xxx/soc.c Line:50 CONSTANT_COMPARISON: Comparisons should place the constant on the right side of the test File:soc/arm/ti_mspm0/mspm0g3xxx/soc.c Line:52 BLOCK_COMMENT_STYLE: Block comments use * on subseque

See https://docs.zephyrproject.org/latest/contribute/guidelines.html#commit-guidelines for more details 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: author email (Luis Reynoso <[email protected]>) needs to match one of the signed-off-by entries. de32fcd11db06a044524d84f6b021d04861ea97f: author email (Luis Reynoso <[email protected]>) needs to match one of the signed-off-by entries.

See https://www.pylint.org/ for more details I0021:Useless suppression of 'undefined-loop-variable' (useless-suppression) File:scripts/footprint/fpdiff.py Line:56 Column:0 E0611:No name 'ZEPHYR_BASE' in module 'conftest' (no-name-in-module) File:scripts/tests/twister/test_handlers.py Line:24 Column:0 E0611:No name 'ZEPHYR_BASE' in module 'conftest' (no-name-in-module) File:scripts/tests/twister_blackbox/test_hardwaremap.py Line:15 Column:0 E0611:No name 'testsuite_filename_mock' in module 'conftest' (no-name-in-module) File:scripts/tests/twister_blackbox/test_hardwaremap.py Line:15 Column:0 E0611:No name 'TEST_DATA' in module 'conftest' (no-name-in-module) File:scripts/tests/twister_blackbox/test_qemu.py Line:17 Column:0 E0611:No name 'ZEPHYR_BASE' in module 'conftest' (no-name-in-module) File:scripts/tests/twister_blackbox/test_qemu.py Line:17 Column:0 E0611:No name 'testsuite_filename_mock' in module 'conftest' (no-name-in-module) File:scripts/tests/twister_blackbox/test_qemu.py Line:17 Column:0 E0611:No name 'Endpoint' in module 'conftest' (no-name-in-module) File:tests/net/lib/lwm2m/interop/pytest/test_bootstrap.py Line:22 Column:0 R0801:Similar lines in 2 files File:tests/subsys/debug/gdbstub/pytest/test_gdbstub.py Line:1 Column:0

See https://docs.zephyrproject.org/latest/contribute/guidelines.html#commit-guidelines for more details Commit 6e13e920de: 1: UC2 Commit message does not contain a 'Signed-off-by:' line 1: UC3 Commit title does not follow [subsystem]: [subject] (and should not start with literal subsys:): "Add option to use HFXT or PLL for CAN" 1: UC6 Commit message body is empty, should at least have 1 line(s). 3: B6 Body message is missing Commit de32fcd11d: 1: UC2 Commit message does not contain a 'Signed-off-by:' line 1: UC3 Commit title does not follow [subsystem]: [subject] (and should not start with literal subsys:): "Fixes after rebasing and twister tests" 1: UC6 Commit message body is empty, should at least have 1 line(s). 3: B6 Body message is missing

See https://docs.zephyrproject.org/latest/contribute/guidelines.html#coding-style for more details. Please remove blank lines at end of 'tests/lib/c_lib/common/README.txt'

Git conflict markers and whitespace errors are not allowed in added changes 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: drivers/can/can_mspm0g3xxx_canfd.c:104: trailing whitespace. 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: drivers/can/can_mspm0g3xxx_canfd.c:118: trailing whitespace. 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: soc/arm/ti_mspm0/mspm0g3xxx/soc.c:48: trailing whitespace. 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: Note: Clock Control driver is not available yet for MSPM0. 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: soc/arm/ti_mspm0/mspm0g3xxx/soc.c:49: trailing whitespace. 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: soc/arm/ti_mspm0/mspm0g3xxx/soc.c:50: trailing whitespace. 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: soc/arm/ti_mspm0/mspm0g3xxx/soc.h:20: trailing whitespace. 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: soc/arm/ti_mspm0/mspm0g3xxx/soc.h:21: trailing whitespace. 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: Note: Clock Control driver is not available yet for MSPM0. 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: soc/arm/ti_mspm0/mspm0g3xxx/soc.h:22: trailing whitespace. 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: soc/arm/ti_mspm0/mspm0g3xxx/soc.h:23: trailing whitespace. 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: soc/arm/ti_mspm0/mspm0g3xxx/soc.h:28: trailing whitespace. 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: soc/arm/ti_mspm0/mspm0g3xxx/soc.h:38: trailing whitespace. 6e13e920dedbe3700eaa4f7ab98b21581f0505ec: soc/arm/ti_mspm0/mspm0g3xxx/soc.h:46: trailing whitespace.

See https://docs.zephyrproject.org/latest/build/kconfig/tips.html for more details. Found references to undefined Kconfig symbols. If any of these are false positives, then add them to UNDEF_KCONFIG_WHITELIST in /home/runner/work/zephyr/zephyr/./scripts/ci/check_compliance.py. If the reference is for a comment like /* CONFIG_FOO_* */ (or /* CONFIG_FOO_*_... */), then please use exactly that form (with the '*'). The CI check knows not to flag it. More generally, a reference followed by $, @, {, *, or ## will never be flagged. CONFIG_ZTEST_NEW_API tests/drivers/i2c/i2c_target_api2/prj.conf:3

Process completed with exit code 1.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

arch/arm/core/cortex_a_r/smp.c:80 'maping' may be misspelled - perhaps 'mapping'?

drivers/can/can_mspm0g3xxx_canfd.c:77 Comparisons should place the constant on the right side of the test

drivers/can/can_mspm0g3xxx_canfd.c:92 Comparisons should place the constant on the right side of the test

drivers/can/can_mspm0g3xxx_canfd.c:104 Comparisons should place the constant on the right side of the test

drivers/crypto/crypto_smartbond.c:386 'perfomance' may be misspelled - perhaps 'performance'?

drivers/dma/dma_smartbond.c:90 'retrived' may be misspelled - perhaps 'retrieved'?

drivers/dma/dma_smartbond.c:268 'perfomance' may be misspelled - perhaps 'performance'?

drivers/dma/dma_smartbond.c:468 'Inavlid' may be misspelled - perhaps 'Invalid'?

drivers/dma/dma_smartbond.c:548 'Inavlid' may be misspelled - perhaps 'Invalid'?