TEST: rpmsg: glink: CI pipeline validation commit - do not merge

[Vishnu Santhosh (quic-vishsant)]

This commit is added purely to validate Dev-CI pipeline behaviour for the tech/mproc/rpmsg topic branch. Specifically, it tests whether pre-merge rootfs generation is restored.

This commit should NOT be merged and must be reverted after testing.

[qlijarvis]

PR #1432 — validate-patch

PR: #1432

Verdict	Issues	Detailed Report
❌	4	Full report

Final Summary

1. Lore link present: No — TEST: prefix; this is a CI validation commit, not posted upstream
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — test-only commit, never intended for upstream submission
4. PR present in qcom-next: Not checked — TEST: commit explicitly marked "do not merge"

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #1432 - TEST: rpmsg: glink: CI pipeline validation commit - do not merge
Upstream commit: N/A
Verdict: ❌ FAIL

Commit Message

Check	Status	Note
Subject matches upstream	N/A	Test commit, not intended for upstream
Body preserves rationale	✅	Clear explanation of test purpose
Fixes tag present/correct	N/A	Not a bug fix
Authorship preserved	✅	Authored by Vishnu Santhosh
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
drivers/rpmsg/qcom_glink_smem.c	❌	Trivial cosmetic change to MODULE_DESCRIPTION for testing only

Issues

• Critical: Not intended for merge — Commit message explicitly states "This commit should NOT be merged and must be reverted after testing"
• Purpose: CI/Dev-CI testing only — This is a test commit to validate Dev-CI pipeline behavior for tech/mproc/rpmsg topic branch, specifically testing pre-merge rootfs generation
• Trivial change with no functional value — Adds "[CI-TEST: dev-ci rootfs validation]" suffix to MODULE_DESCRIPTION string, which serves no purpose beyond triggering CI
• Subject prefix "TEST:" — Clearly marks this as a test commit not suitable for production branches

Verdict

REJECT — Do not merge. This is an explicit test commit created solely to validate CI pipeline behavior and must be reverted after testing completes.

Final Summary

1. Lore link present: No — TEST: prefix; this is a CI validation commit, not posted upstream
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: N/A — test-only commit, never intended for upstream submission
4. PR present in qcom-next: Not checked — TEST: commit explicitly marked "do not merge"

[qlijarvis]

PR #1432 — checker-log-analyzer

PR: #1432
Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/28380954326

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues detected
dt-binding-check	⏭️	Skipped - no DT binding changes
dtb-check	⏭️	Skipped - no devicetree changes
sparse-check	✅	Build completed successfully
check-uapi-headers	✅	No UAPI header changes
check-patch-compliance	❌	Subject prefix missing
tag-check	N/A	Not applicable for topic branches
qcom-next-check	N/A	Not applicable for topic branches

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1432 - TEST: rpmsg: glink: CI pipeline validation commit - do not merge
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/28380954326

Checker	Result	Summary
checkpatch	✅	No style issues detected
dt-binding-check	⏭️	Skipped - no DT binding changes
dtb-check	⏭️	Skipped - no devicetree changes
sparse-check	✅	Build completed successfully
check-uapi-headers	✅	No UAPI header changes
check-patch-compliance	❌	Subject prefix missing
tag-check	N/A	Not applicable for topic branches
qcom-next-check	N/A	Not applicable for topic branches

❌ check-patch-compliance

Root cause: Commit subject line TEST: rpmsg: glink: CI pipeline validation commit - do not merge does not start with a required prefix (UPSTREAM:, FROMLIST:, BACKPORT:, or FROMGIT:).

Failure details:

2026-06-29T15:07:56.7155674Z Checking commit: TEST: rpmsg: glink: CI pipeline validation commit - do not merge
2026-06-29T15:07:56.7170285Z Commit summary does not start with a required prefix
2026-06-29T15:07:56.7171008Z Leaving /opt/actions-runner/_work/kernel-config/kernel-config/kernel
2026-06-29T15:07:56.7171683Z /opt/actions-runner/_work/kernel-config/kernel-config
2026-06-29T15:07:56.7185948Z ##[error]Process completed with exit code 1.

The check-patch-compliance checker enforces that all commits in topic branches must have one of the following prefixes in their subject line:

• UPSTREAM: - for patches already merged in mainline
• FROMLIST: - for patches posted to upstream mailing lists but not yet merged
• BACKPORT: - for patches backported from a newer kernel version
• FROMGIT: - for patches cherry-picked from another git tree

The current commit uses TEST: as a prefix, which is not recognized by the compliance checker.

Fix:

Since this is explicitly a test commit that should not be merged (as stated in the commit message), you have two options:

1. Add a compliant prefix - Change the subject to use a recognized prefix:

   FROMLIST: rpmsg: glink: CI pipeline validation commit - do not merge
   

   or

   BACKPORT: rpmsg: glink: CI pipeline validation commit - do not merge
   

2. Target a different branch - If this PR is intended for qcom-next or qcom-next-staging branches (which don't require these prefixes), retarget the PR accordingly.

Reproduce locally:

git clone https://github.com/qualcomm-linux/kernel-checkers.git
cd kernel-checkers
./check-patch-compliance.sh --kernel-src <path-to-kernel> --base <base-sha> --head <head-sha>

Verdict

1 blocker to fix: The commit subject must be updated with a compliant prefix (UPSTREAM:, FROMLIST:, BACKPORT:, or FROMGIT:) before this PR can be merged into a topic branch. All other checkers passed successfully.