Skip to content

Instantly share code, notes, and snippets.

@qlijarvis

qlijarvis/pr_only_checker_log_detailed.md

Created November 6, 2026 07:10
Show Gist options

  • Select an option

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

Select an option

Learn more about clone URLs
Save qlijarvis/ff4de25e63b6b32606c12c5c49944d48 to your computer and use it in GitHub Desktop.
Download ZIP
PR #2203 checker-log-analyzer detailed analysis
Raw
pr_only_checker_log_detailed.md

PR #2203 — checker-log-analyzer Detailed Analysis

PR: qualcomm-linux/kernel-topics#2203 Checker run: https://github.com/qualcomm-linux/kernel-config/actions/runs/42171485805

Report

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #2203 - PENDING: arm64: dts: qcom: purwa-evk: add QPS615 m.2 ethernet staging overlay
Target branch: tech/overlay/dt
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/42171485805

Checker Result Summary
checkpatch ⚠️ CI infrastructure failure - unable to run
dt-binding-check ⚠️ CI infrastructure failure - unable to run
dtb-check ⚠️ CI infrastructure failure - unable to run
sparse-check ⚠️ CI infrastructure failure - unable to run
check-uapi-headers ⚠️ CI infrastructure failure - unable to run
check-patch-compliance ❌ Would fail: PENDING: prefix not allowed, missing Link: tag
tag-check ✅ PENDING: is a valid prefix for non-qcom-next branches

⚠️ CI Infrastructure Failure

Root cause: All checker jobs failed during the merge step with fatal: refusing to merge unrelated histories.

Failure details:

2026-11-06T06:16:27.4203303Z Fetching PR #2203 from https://github.com/qualcomm-linux/kernel-topics.git...
2026-11-06T06:16:28.1788849Z From https://github.com/qualcomm-linux/kernel-topics
2026-11-06T06:16:28.1789441Z  * [new ref]                   refs/pull/2203/head -> pr-2203
2026-11-06T06:16:28.1989078Z Merging pr-2203 (no-commit)...
2026-11-06T06:16:48.4335491Z fatal: refusing to merge unrelated histories
2026-11-06T06:16:48.5463595Z Merge failed or conflicts detected. Aborting merge.

Analysis: The CI workflow attempts to:

  1. Create an integration branch from qcom-next baseline (commit 17bbb4b37bbc)
  2. Merge topic branch topic/tech/overlay/dt
  3. Merge PR #2203

The failure occurs at step 3 when trying to merge the PR. The error "refusing to merge unrelated histories" indicates that the PR branch (tech/overlay/dt) has a completely different commit history that doesn't share a common ancestor with the integration branch.

This is a CI workflow configuration issue, not a patch defect.

Fix: The PR branch needs to be rebased onto a commit that shares history with the qcom-next baseline, or the CI workflow needs to use --allow-unrelated-histories when merging topic branches.

Reproduce locally:

git clone https://github.com/qualcomm-linux/kernel.git
cd kernel
git checkout -b integ 17bbb4b37bbc4fc5827b4667445a0c43967c0f48
git fetch https://github.com/qualcomm-linux/kernel-topics.git pull/2203/head:pr-2203
git merge pr-2203  # Will fail with "refusing to merge unrelated histories"

❌ check-patch-compliance (predicted failure)

Root cause: The commit uses the PENDING: prefix, which is not in the checker's allowed list.

Failure details:

Commit: acd40d95ecf2d8e95211efc2111b62bdc2bcf5cf
Subject: PENDING: arm64: dts: qcom: purwa-evk: add QPS615 m.2 ethernet staging overlay

The check-patch-compliance checker only accepts these prefixes:

  • FROMLIST: - Patch posted to mailing list
  • FROMGIT: - Patch from maintainer tree
  • UPSTREAM: - Patch merged into mainline
  • BACKPORT: - Backported with modifications

Additionally, the commit message lacks a Link: tag pointing to an upstream lore.kernel.org URL.

Fix:

Option 1 (if the patch has been posted upstream):

git rebase -i HEAD~1  # mark commit as 'edit'
git commit --amend -m "FROMLIST: arm64: dts: qcom: purwa-evk: add QPS615 m.2 ethernet staging overlay

Add purwa-evk-staging.dtso for the QPS615 m.2 e-key daughter card.
When installed, the QPS615 PCIe switch replaces the direct WLAN connection.
The overlay describes dual Ethernet (TC956X) at QPS615 downstream port 4
(pci@4,0, bus 5 dev 0 fn0/fn1).

Link: https://lore.kernel.org/...
Signed-off-by: Shirisha Ramireddy <sramired@qti.qualcomm.com>"
git rebase --continue

Option 2 (if this is vendor-only work-in-progress): Use QCLINUX: prefix instead (though note that check-patch-compliance will still fail for vendor-only commits - this is a known checker limitation):

git commit --amend -m "QCLINUX: arm64: dts: qcom: purwa-evk: add QPS615 m.2 ethernet staging overlay
..."

Note: The PENDING: prefix is valid for the tag-check requirement (all commits to non-qcom-next branches must have a prefix), but it's not accepted by check-patch-compliance. This is a known limitation where vendor-internal prefixes (PENDING:, QCLINUX:) will always fail the compliance checker.

Reproduce locally:

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

✅ tag-check

Status: PASS

Analysis: The target branch is tech/overlay/dt, which is not qcom-next or qcom-next-staging. Therefore, every commit must start with a valid prefix tag.

The commit subject starts with PENDING:, which is one of the accepted prefixes:

  • FROMLIST: ✓
  • FROMGIT: ✓
  • UPSTREAM: ✓
  • BACKPORT: ✓
  • QCLINUX: ✓
  • PENDING: ✓ (used in this PR)
  • WORKAROUND: ✓

Verdict: ✅ PASS - The subject-line prefix requirement is satisfied.

📋 Patch Content Analysis

Since the checkers couldn't run, here's a manual review of the patch content:

Commit: acd40d95ecf2d8e95211efc2111b62bdc2bcf5cf

Changes:

  • ✅ SPDX license header present (BSD-3-Clause)
  • ✅ Signed-off-by present
  • ✅ DTS overlay syntax appears correct
  • ✅ No obvious checkpatch style violations
  • ✅ No C/H files changed (sparse-check and check-uapi-headers would skip)
  • ✅ No binding changes (dt-binding-check would skip)
  • ⚠️ dtb-check would need to run to validate the PCI node structure

Potential concerns:

  1. The PCI node structure uses pci@0,0, pci@3,0, pci@0,1 - these should be validated against PCI DT bindings
  2. The qps615 node acts as both a PCI device and a GPIO controller - ensure this is supported by the hardware
  3. The phy-reset-gpios properties reference &qps615 - verify this phandle is valid in the context where the overlay is applied

Verdict

CI Infrastructure Issue: The workflow failed due to "unrelated histories" when attempting to merge the PR. This must be resolved before any checkers can run.

Predicted Checker Results:

  • ❌ 1 blocker: check-patch-compliance will fail due to PENDING: prefix and missing Link: tag
  • ✅ tag-check: PASS (prefix requirement satisfied)
  • ⏭️ 3 checkers would skip: dt-binding-check, sparse-check, check-uapi-headers (no relevant file changes)
  • ⚠️ 2 checkers need to run: checkpatch (likely pass), dtb-check (needs validation)

Recommended actions:

  1. Immediate: Fix the CI merge issue by rebasing the PR branch onto a commit that shares history with qcom-next
  2. Before merge: Change PENDING: to FROMLIST: (if posted upstream) or QCLINUX: (if vendor-only) and add a Link: tag if applicable
  3. Validation: Re-trigger CI to run dtb-check and verify PCI node structure

Raw agent output

Perfect! The target branch is tech/overlay/dt. This is NOT qcom-next or qcom-next-staging, so the tag-check DOES apply.

Now I have all the information I need to produce the final report:

[CHECKER_LOG_REPORT]

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #2203 - PENDING: arm64: dts: qcom: purwa-evk: add QPS615 m.2 ethernet staging overlay
Target branch: tech/overlay/dt
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/42171485805

Checker Result Summary
checkpatch ⚠️ CI infrastructure failure - unable to run
dt-binding-check ⚠️ CI infrastructure failure - unable to run
dtb-check ⚠️ CI infrastructure failure - unable to run
sparse-check ⚠️ CI infrastructure failure - unable to run
check-uapi-headers ⚠️ CI infrastructure failure - unable to run
check-patch-compliance ❌ Would fail: PENDING: prefix not allowed, missing Link: tag
tag-check ✅ PENDING: is a valid prefix for non-qcom-next branches

⚠️ CI Infrastructure Failure

Root cause: All checker jobs failed during the merge step with fatal: refusing to merge unrelated histories.

Failure details:

2026-11-06T06:16:27.4203303Z Fetching PR #2203 from https://github.com/qualcomm-linux/kernel-topics.git...
2026-11-06T06:16:28.1788849Z From https://github.com/qualcomm-linux/kernel-topics
2026-11-06T06:16:28.1789441Z  * [new ref]                   refs/pull/2203/head -> pr-2203
2026-11-06T06:16:28.1989078Z Merging pr-2203 (no-commit)...
2026-11-06T06:16:48.4335491Z fatal: refusing to merge unrelated histories
2026-11-06T06:16:48.5463595Z Merge failed or conflicts detected. Aborting merge.

Analysis: The CI workflow attempts to:

  1. Create an integration branch from qcom-next baseline (commit 17bbb4b37bbc)
  2. Merge topic branch topic/tech/overlay/dt
  3. Merge PR #2203

The failure occurs at step 3 when trying to merge the PR. The error "refusing to merge unrelated histories" indicates that the PR branch (tech/overlay/dt) has a completely different commit history that doesn't share a common ancestor with the integration branch.

This is a CI workflow configuration issue, not a patch defect.

Fix: The PR branch needs to be rebased onto a commit that shares history with the qcom-next baseline, or the CI workflow needs to use --allow-unrelated-histories when merging topic branches.

Reproduce locally:

git clone https://github.com/qualcomm-linux/kernel.git
cd kernel
git checkout -b integ 17bbb4b37bbc4fc5827b4667445a0c43967c0f48
git fetch https://github.com/qualcomm-linux/kernel-topics.git pull/2203/head:pr-2203
git merge pr-2203  # Will fail with "refusing to merge unrelated histories"

❌ check-patch-compliance (predicted failure)

Root cause: The commit uses the PENDING: prefix, which is not in the checker's allowed list.

Failure details:

Commit: acd40d95ecf2d8e95211efc2111b62bdc2bcf5cf
Subject: PENDING: arm64: dts: qcom: purwa-evk: add QPS615 m.2 ethernet staging overlay

The check-patch-compliance checker only accepts these prefixes:

  • FROMLIST: - Patch posted to mailing list
  • FROMGIT: - Patch from maintainer tree
  • UPSTREAM: - Patch merged into mainline
  • BACKPORT: - Backported with modifications

Additionally, the commit message lacks a Link: tag pointing to an upstream lore.kernel.org URL.

Fix:

Option 1 (if the patch has been posted upstream):

git rebase -i HEAD~1  # mark commit as 'edit'
git commit --amend -m "FROMLIST: arm64: dts: qcom: purwa-evk: add QPS615 m.2 ethernet staging overlay

Add purwa-evk-staging.dtso for the QPS615 m.2 e-key daughter card.
When installed, the QPS615 PCIe switch replaces the direct WLAN connection.
The overlay describes dual Ethernet (TC956X) at QPS615 downstream port 4
(pci@4,0, bus 5 dev 0 fn0/fn1).

Link: https://lore.kernel.org/...
Signed-off-by: Shirisha Ramireddy <sramired@qti.qualcomm.com>"
git rebase --continue

Option 2 (if this is vendor-only work-in-progress): Use QCLINUX: prefix instead (though note that check-patch-compliance will still fail for vendor-only commits - this is a known checker limitation):

git commit --amend -m "QCLINUX: arm64: dts: qcom: purwa-evk: add QPS615 m.2 ethernet staging overlay
..."

Note: The PENDING: prefix is valid for the tag-check requirement (all commits to non-qcom-next branches must have a prefix), but it's not accepted by check-patch-compliance. This is a known limitation where vendor-internal prefixes (PENDING:, QCLINUX:) will always fail the compliance checker.

Reproduce locally:

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

✅ tag-check

Status: PASS

Analysis: The target branch is tech/overlay/dt, which is not qcom-next or qcom-next-staging. Therefore, every commit must start with a valid prefix tag.

The commit subject starts with PENDING:, which is one of the accepted prefixes:

  • FROMLIST: ✓
  • FROMGIT: ✓
  • UPSTREAM: ✓
  • BACKPORT: ✓
  • QCLINUX: ✓
  • PENDING: ✓ (used in this PR)
  • WORKAROUND: ✓

Verdict: ✅ PASS - The subject-line prefix requirement is satisfied.

📋 Patch Content Analysis

Since the checkers couldn't run, here's a manual review of the patch content:

Commit: acd40d95ecf2d8e95211efc2111b62bdc2bcf5cf

Changes:

  • ✅ SPDX license header present (BSD-3-Clause)
  • ✅ Signed-off-by present
  • ✅ DTS overlay syntax appears correct
  • ✅ No obvious checkpatch style violations
  • ✅ No C/H files changed (sparse-check and check-uapi-headers would skip)
  • ✅ No binding changes (dt-binding-check would skip)
  • ⚠️ dtb-check would need to run to validate the PCI node structure

Potential concerns:

  1. The PCI node structure uses pci@0,0, pci@3,0, pci@0,1 - these should be validated against PCI DT bindings
  2. The qps615 node acts as both a PCI device and a GPIO controller - ensure this is supported by the hardware
  3. The phy-reset-gpios properties reference &qps615 - verify this phandle is valid in the context where the overlay is applied

Verdict

CI Infrastructure Issue: The workflow failed due to "unrelated histories" when attempting to merge the PR. This must be resolved before any checkers can run.

Predicted Checker Results:

  • ❌ 1 blocker: check-patch-compliance will fail due to PENDING: prefix and missing Link: tag
  • ✅ tag-check: PASS (prefix requirement satisfied)
  • ⏭️ 3 checkers would skip: dt-binding-check, sparse-check, check-uapi-headers (no relevant file changes)
  • ⚠️ 2 checkers need to run: checkpatch (likely pass), dtb-check (needs validation)

Recommended actions:

  1. Immediate: Fix the CI merge issue by rebasing the PR branch onto a commit that shares history with qcom-next
  2. Before merge: Change PENDING: to FROMLIST: (if posted upstream) or QCLINUX: (if vendor-only) and add a Link: tag if applicable
  3. Validation: Re-trigger CI to run dtb-check and verify PCI node structure

[/CHECKER_LOG_REPORT]

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