Even if the doc suggests to use the 3rd level, it looks like other
Actions use the 2nd level.

Do the same on our side not to have our summary included under another
one.

Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
---

Notes:
    Sorry for the noise: I usually don't send patches for modifications
    touching the CI files -- mainly because it is quite specific, and our
    team is too small to have multiple people working on that, and reviewing
    these modifications too -- but here we wanted to validate Patchew after
    having applied a hot patch with Davide: the goal is not to re-apply
    patches when tags -- Reviewed-by, etc. -- are shared on the ML, not to
    waste CI resources.

 .github/workflows/checkpatch.yml | 2 +-
 .github/workflows/tests.yml      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/checkpatch.yml b/.github/workflows/checkpatch.yml
index df31d122d674..f70de5d1bfda 100644
--- a/.github/workflows/checkpatch.yml
+++ b/.github/workflows/checkpatch.yml
@@ -45,7 +45,7 @@ jobs:
         if: always()
         run: |
           if [ -s "${{ env.DETAILS }}" ]; then
-            echo '### Results' >> $GITHUB_STEP_SUMMARY
+            echo '## Results' >> $GITHUB_STEP_SUMMARY
             cat "${{ env.DETAILS }}" >> $GITHUB_STEP_SUMMARY
           fi
 
diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.yml
index e12bba92b4ee..4a406ec5f687 100644
--- a/.github/workflows/tests.yml
+++ b/.github/workflows/tests.yml
@@ -72,7 +72,7 @@ jobs:
         if: always()
         run: |
           if [ -s "conclusion.txt" ]; then
-            echo '### Conclusion' >> $GITHUB_STEP_SUMMARY
+            echo '## Conclusion' >> $GITHUB_STEP_SUMMARY
             cat "conclusion.txt" >> $GITHUB_STEP_SUMMARY
           fi
 

base-commit: 52e05de42e1094a943053af93ea08c51a44091f7
-- 
2.43.0