Skip to content

Instantly share code, notes, and snippets.

@qlijarvis

qlijarvis/pr_only_validate_patch_detailed.md

Created November 6, 2026 07:25
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save qlijarvis/eab3c6b6c23e4d3275062e81f3128ab0 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save qlijarvis/eab3c6b6c23e4d3275062e81f3128ab0 to your computer and use it in GitHub Desktop.
Download ZIP
PR #2176 validate-patch detailed analysis
Raw
pr_only_validate_patch_detailed.md

PR #2176 — validate-patch Detailed Analysis

PR: qualcomm-linux/kernel-topics#2176

Report

🔍 Patch Validation

PR: #2176 - QCLINUX: arm64: dts: qcom: add Nord CAMX EL2 overlay
Upstream commit: N/A (vendor-only QCLINUX: commit)
Verdict: ❌ FAIL

Commit Message

Check Status Note
Subject matches upstream N/A Vendor-only commit; no upstream source
Body preserves rationale ✅ Clear description of EL2 boot support for Nord platforms
Fixes tag present/correct N/A New feature, not a fix
Authorship preserved ✅ Signed-off-by present
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds build rules for nord-camx-el2 composite DTBs
arch/arm64/boot/dts/qcom/nord-camx-el2.dtso ✅ New overlay for CAMX EL2 configuration

Issues

  • Integration presence FAIL: Commit is missing from both qcom-next and kernel-topics branches. For a QCLINUX: vendor commit, it should be present in at least one of these integration branches before the PR is merged.

Verdict

Do not merge until this commit is present in qcom-next or the appropriate kernel-topics branch. The commit itself is well-formed, but the integration presence check failed.

Final Summary

  1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: N/A — vendor-only change, not posted upstream
  4. PR present in qcom-next/topics: Fail — 1/1 commit(s) are missing from both qcom-next and topics (per integration_presence_report.md)

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs. It is the authoritative source for whether PR changes are already present in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel qcom-next ref: 17bbb4b37bbc4fc5827b4667445a0c43967c0f48 topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics topics fetch: fetched

Commit Subject qcom-next topics Final
1/1 [PATCH] QCLINUX: arm64: dts: qcom: add Nord CAMX EL2 overlay missing - no subject, patch-id, or full tree-content match found missing - no subject, patch-id, or full tree-content match found missing

Final Status

overall_status: FAIL present_commits: 0/1 partial_commits: 0/1 missing_commits: 1/1 topics_checked_for_commits: 1/1 final_summary: PR present in qcom-next/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

Raw agent output

Perfect! Now I have all the information needed. Let me analyze this PR following the validate-patch skill workflow:

Step 1 — Parse the PR and Check for Lore Link

The commit has:

  • Subject: QCLINUX: arm64: dts: qcom: add Nord CAMX EL2 overlay
  • Prefix: QCLINUX:
  • No lore.kernel.org link in the commit message

According to the skill, QCLINUX: prefix indicates a vendor-only commit with no upstream lore link expected. The skill explicitly states: "QCLINUX:, PENDING:, WORKAROUND: prefixes indicate vendor-only commits with no upstream lore link — bail out with a note that validation is not applicable for these."

Analysis:

This is a QCLINUX: vendor-only commit that:

  1. Adds a new device tree overlay file (nord-camx-el2.dtso) for EL2 boot support
  2. Updates the Makefile to build the new overlay and composite DTBs
  3. Has no lore link (expected and correct for QCLINUX: prefix)
  4. Is not present in qcom-next or topics (per integration_presence_report.md)

For vendor-only commits, the validation scope is limited to:

  • Commit message format correctness
  • Code quality (not applicable here - this is a straightforward DTS addition)
  • Integration presence (FAIL - missing from both qcom-next and topics)

[VALIDATE_PATCH_REPORT]

🔍 Patch Validation

PR: #2176 - QCLINUX: arm64: dts: qcom: add Nord CAMX EL2 overlay
Upstream commit: N/A (vendor-only QCLINUX: commit)
Verdict: ❌ FAIL

Commit Message

Check Status Note
Subject matches upstream N/A Vendor-only commit; no upstream source
Body preserves rationale ✅ Clear description of EL2 boot support for Nord platforms
Fixes tag present/correct N/A New feature, not a fix
Authorship preserved ✅ Signed-off-by present
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
arch/arm64/boot/dts/qcom/Makefile ✅ Adds build rules for nord-camx-el2 composite DTBs
arch/arm64/boot/dts/qcom/nord-camx-el2.dtso ✅ New overlay for CAMX EL2 configuration

Issues

  • Integration presence FAIL: Commit is missing from both qcom-next and kernel-topics branches. For a QCLINUX: vendor commit, it should be present in at least one of these integration branches before the PR is merged.

Verdict

Do not merge until this commit is present in qcom-next or the appropriate kernel-topics branch. The commit itself is well-formed, but the integration presence check failed.

Final Summary

  1. Lore link present: No — QCLINUX: prefix; no lore link expected or required
  2. Lore link matches PR commits: N/A — no lore link to compare against
  3. Upstream patch status: N/A — vendor-only change, not posted upstream
  4. PR present in qcom-next/topics: Fail — 1/1 commit(s) are missing from both qcom-next and topics (per integration_presence_report.md)

[/VALIDATE_PATCH_REPORT]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment