Dummy PR for Testing Orbit App

[sgaud-quic]

Dummy PR

[qlijarvis]

PR #705 — validate-patch

PR: #705

Verdict	Issues	Detailed Report
❌	5	Full report

Final Summary

1. Lore link present: No — no Link tag or lore reference found in commit message
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: Not upstream — explicitly labeled as dummy/test patch; trivial README change would never be accepted upstream
4. PR present in qcom-next: Not checked — test patch should not be merged to any branch

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #705 - Dummy PR for Testing Orbit App
Upstream commit: N/A
Verdict: ❌ FAIL

Commit Message

Check	Status	Note
Subject matches upstream	❌	No upstream reference; test patch not suitable for kernel tree
Body preserves rationale	❌	Empty body; no technical justification provided
Fixes tag present/correct	N/A	Not a bug fix
Authorship preserved	✅	Author and SOB present
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
README	❌	Trivial test change with no technical merit

Issues

• Missing commit body: Commit message has no body text explaining the change rationale
• Non-technical change: Modifying README with "Test" prefix serves no kernel development purpose
• No upstream reference: No Link tag, no lore.kernel.org reference, no indication of upstream origin
• Test/dummy nature: Subject explicitly states "Dummy PR for Testing Orbit App" — not a legitimate kernel patch
• Violates kernel standards: Kernel commits must have technical merit and proper justification

Verdict

Reject — this is an explicitly labeled test/dummy patch with no technical merit, missing commit body, and unsuitable for any kernel tree.

Final Summary

1. Lore link present: No — no Link tag or lore reference found in commit message
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: Not upstream — explicitly labeled as dummy/test patch; trivial README change would never be accepted upstream
4. PR present in qcom-next: Not checked — test patch should not be merged to any branch

[qlijarvis]

PR #705 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	Missing commit description warning
dt-binding-check	⏭️	Skipped (no DT binding changes)
dtb-check	⏭️	Skipped (no devicetree changes)
sparse-check	⏭️	Skipped (no C source changes)
check-uapi-headers	⏭️	Skipped (no UAPI header changes)
check-patch-compliance	❌	Missing required subject prefix
tag-check	N/A	Not applicable for qcom-6.18.y branch
qcom-next-check	N/A	Not applicable for qcom-6.18.y branch

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #705 - Dummy PR for Testing Orbit App
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/27363053089

Checker	Result	Summary
checkpatch	❌	Missing commit description warning
dt-binding-check	⏭️	Skipped (no DT binding changes)
dtb-check	⏭️	Skipped (no devicetree changes)
sparse-check	⏭️	Skipped (no C source changes)
check-uapi-headers	⏭️	Skipped (no UAPI header changes)
check-patch-compliance	❌	Missing required subject prefix
tag-check	N/A	Not applicable for qcom-6.18.y branch
qcom-next-check	N/A	Not applicable for qcom-6.18.y branch

---

❌ checkpatch

Root cause: Commit message lacks a proper description body (only has subject line and Signed-off-by).

Failure details:

WARNING: Missing commit description - Add an appropriate one

2cbe93afb1bbf34acf884cdc68746609ea43c570 total: 0 errors, 1 warnings, 0 checks, 5 lines checked

Commit 2cbe93afb1bb ("Dummy PR for Testing Orbit App") has style problems, please review.

Fix: Add a commit message body between the subject line and the Signed-off-by trailer. The body should explain:

• What the change does
• Why the change is needed
• Any relevant context

Example format:

Dummy PR for Testing Orbit App

This is a test commit to validate the Orbit App integration
with the kernel CI workflow. It makes a trivial change to
the README file for testing purposes.

Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>

Reproduce locally:

./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES --git 055ce4ebf97baac453456414a4e25cd05134ac84..2cbe93afb1bbf34acf884cdc68746609ea43c570

---

❌ check-patch-compliance

Root cause: Commit subject does not start with a required prefix (UPSTREAM:, FROMLIST:, BACKPORT:, or FROMGIT:).

Failure details:

Checking commit: Dummy PR for Testing Orbit App
Commit summary does not start with a required prefix

Fix: For the qcom-6.18.y branch, all commits must have a subject prefix indicating their origin:

• UPSTREAM: - Patch already merged in mainline Linux
• FROMLIST: - Patch posted to upstream mailing list but not yet merged
• BACKPORT: - Patch backported from a newer kernel version
• FROMGIT: - Patch from a maintainer's git tree (not yet in mainline)

Since this is a test commit not from upstream, you should either:

1. Use FROMLIST: prefix if this represents a patch that would be posted upstream
2. Use UPSTREAM: prefix if this represents an already-merged upstream patch
3. Consider if this test commit should target a different branch (qcom-next or qcom-next-staging) where prefix requirements may differ

Example:

FROMLIST: Dummy PR for Testing Orbit App

Reproduce locally:

# Check the check-patch-compliance.sh script in kernel-checkers repo
bash kernel-checkers/check-patch-compliance.sh --kernel-src . --base 055ce4ebf97baac453456414a4e25cd05134ac84 --head 2cbe93afb1bbf34acf884cdc68746609ea43c570

---

Verdict

2 blockers must be fixed before merge:

1. Add a proper commit message body (checkpatch warning)
2. Add required subject prefix: UPSTREAM:/FROMLIST:/BACKPORT:/FROMGIT: (check-patch-compliance failure)

All other checkers were appropriately skipped as the PR only modifies the README file (no DT, C source, or UAPI changes).

[rohitbhopatkar]

test

[qswat-orbit-external]

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.