scripts: checkpatch: fix missing blank line detection after declarations

[vignesh-aerlync]

Fix checkpatch not warning when blank line after declaration
is removed. Updated regexes to also handle context lines,
ensuring consistent detection.

Fixes: #98976

[Thalley]

@vignesh-aerlync I tried cherry-picking the offending commit from #98406 that caused me to create the reference issue, and then cherry-picked your commit here, but checkpatch.pl still does not fail. How did you test your changes?

[Thalley]

Does not seem to fix the issue

[vignesh-aerlync]

@vignesh-aerlync I tried cherry-picking the offending commit from #98406 that caused me to create the reference issue, and then cherry-picked your commit here, but checkpatch.pl still does not fail. How did you test your changes?

I tested it by modifying an existing source file in Zephyr and creating a dummy commit to verify that checkpatch.pl correctly reports the missing blank line warning.

zephyr_fork/zephyr$ git show | ./scripts/checkpatch.pl 
-:18: WARNING:LINE_SPACING: Missing a blank line after declarations
#18: FILE: samples/sensor/lis2dh/src/main.c:83:
 		int rc;
 		trig.type = SENSOR_TRIG_DATA_READY;

False negative

[Thalley]

The PR seems to fix the issue (after doing proper testing). Not sure whether the changes are valid though, so someone who is more familiar with this should review

[vignesh-aerlync]

@vignesh-aerlync I tried cherry-picking the offending commit from #98406 that caused me to create the reference issue, and then cherry-picked your commit here, but checkpatch.pl still does not fail. How did you test your changes?

Thanks for pointing that out . I tested in #98406 ,my patch missed handling that particular case you mentioned. I’ll update my change accordingly.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud