PR: qualcomm-linux/kernel-topics#2176 Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/42175817102
PR: qualcomm-linux/kernel-topics#2176 Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/42175817102
| # | Error | File:Line | PR-introduced? | Root Cause |
|---|---|---|---|---|
| 1 | fatal: couldn't find remote ref refs/heads/tech/overlay/dt | N/A | No | Pre-existing infrastructure issue: PR targets branch tech/overlay/dt which doesn't exist as a branch (only as tag tech/overlay/dt-7.3-rc2-20261024). Automerge configuration error. |
| 2 | Merge conflicts in arch/arm64/boot/dts/qcom/Makefile | arch/arm64/boot/dts/qcom/Makefile |
Possibly | PR adds nord-camx-el2 entries to Makefile which conflicts with other topic branches during integration. Conflict resolution needed. |
No compilation errors occurred. The build failed during the pre-compilation automerge/integration phase due to: (1) a missing branch reference causing git fetch failure, and (2) merge conflicts in the Makefile. The PR changes themselves are syntactically valid but require conflict resolution with the integration baseline.
PR: qualcomm-linux/kernel-topics#2176 Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/42175817102
Location: Git remote fetch operation Error message:
fatal: couldn't find remote ref refs/heads/tech/overlay/dt
error: Could not fetch tech/overlay/dt
PR-introduced: No
Reason: This is a pre-existing infrastructure/configuration issue. The PR targets the branch tech/overlay/dt, but this branch does not exist in the remote repository https://github.com/qualcomm-linux-stg/kernel-topics.git. Only the tag tech/overlay/dt-7.3-rc2-20261024 exists. The automerge system attempted to fetch refs/heads/tech/overlay/dt (a branch) but should have been configured to use the tag instead.
Fix: Update the kernel-config automerge configuration to reference the correct tag tech/overlay/dt-7.3-rc2-20261024 instead of the non-existent branch tech/overlay/dt, or create the branch in the upstream repository.
Location: arch/arm64/boot/dts/qcom/Makefile
Error message:
Normal merge conflict for 'Documentation/devicetree/bindings/arm/qcom.yaml':
{local}: modified file
{remote}: modified file
Merge failed, manual merge
PR-introduced: Possibly Reason: The PR adds new Makefile entries for nord-camx-el2 device tree overlays:
nord-ride-embedded-camx-el2-dtbsnord-rrd-camx-el2-dtbsnord-camx-el2.dtbo
These additions conflict with changes from other topic branches being merged during the integration process. The specific conflict occurred in arch/arm64/boot/dts/qcom/Makefile and also in Documentation/devicetree/bindings/arm/qcom.yaml. The automerge process uses git rerere (reuse recorded resolution) which staged some conflicts automatically, but ultimately failed when encountering unresolvable conflicts.
Fix: Rebase the PR branch onto the latest integration baseline (qcom-next-7.3-rc6-20261024 or later) and resolve merge conflicts manually in the Makefile and bindings YAML file.
The build failure is not caused by compilation errors in the PR code itself. The PR introduces valid device tree overlay syntax and Makefile entries. The failure occurred during the pre-compilation integration phase:
- Infrastructure issue: The automerge system cannot fetch the target branch
tech/overlay/dtbecause it doesn't exist (only the tag exists). - Integration conflicts: The PR's Makefile changes conflict with other topic branches being merged simultaneously in the integration pipeline.
No kernel compilation was attempted, so there are no compiler errors, warnings, or device tree compilation issues to report.
- Immediate: Update the PR's target branch configuration or the automerge config to use the correct tag reference
tech/overlay/dt-7.3-rc2-20261024. - Short-term: Rebase the PR onto the latest integration baseline to resolve Makefile conflicts with other topic branches.
- Verification: Re-run the build after fixing the branch reference and resolving conflicts to verify the device tree overlay compiles correctly.
No compilation was attempted. Now let me create the analysis report:
[BUILD_SUMMARY]
PR: qualcomm-linux/kernel-topics#2176 Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/42175817102
| # | Error | File:Line | PR-introduced? | Root Cause |
|---|---|---|---|---|
| 1 | fatal: couldn't find remote ref refs/heads/tech/overlay/dt | N/A | No | Pre-existing infrastructure issue: PR targets branch tech/overlay/dt which doesn't exist as a branch (only as tag tech/overlay/dt-7.3-rc2-20261024). Automerge configuration error. |
| 2 | Merge conflicts in arch/arm64/boot/dts/qcom/Makefile | arch/arm64/boot/dts/qcom/Makefile |
Possibly | PR adds nord-camx-el2 entries to Makefile which conflicts with other topic branches during integration. Conflict resolution needed. |
No compilation errors occurred. The build failed during the pre-compilation automerge/integration phase due to: (1) a missing branch reference causing git fetch failure, and (2) merge conflicts in the Makefile. The PR changes themselves are syntactically valid but require conflict resolution with the integration baseline. [/BUILD_SUMMARY]
[BUILD_DETAILED]
PR: qualcomm-linux/kernel-topics#2176 Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/42175817102
Location: Git remote fetch operation Error message:
fatal: couldn't find remote ref refs/heads/tech/overlay/dt
error: Could not fetch tech/overlay/dt
PR-introduced: No
Reason: This is a pre-existing infrastructure/configuration issue. The PR targets the branch tech/overlay/dt, but this branch does not exist in the remote repository https://github.com/qualcomm-linux-stg/kernel-topics.git. Only the tag tech/overlay/dt-7.3-rc2-20261024 exists. The automerge system attempted to fetch refs/heads/tech/overlay/dt (a branch) but should have been configured to use the tag instead.
Fix: Update the kernel-config automerge configuration to reference the correct tag tech/overlay/dt-7.3-rc2-20261024 instead of the non-existent branch tech/overlay/dt, or create the branch in the upstream repository.
Location: arch/arm64/boot/dts/qcom/Makefile
Error message:
Normal merge conflict for 'Documentation/devicetree/bindings/arm/qcom.yaml':
{local}: modified file
{remote}: modified file
Merge failed, manual merge
PR-introduced: Possibly Reason: The PR adds new Makefile entries for nord-camx-el2 device tree overlays:
nord-ride-embedded-camx-el2-dtbsnord-rrd-camx-el2-dtbsnord-camx-el2.dtbo
These additions conflict with changes from other topic branches being merged during the integration process. The specific conflict occurred in arch/arm64/boot/dts/qcom/Makefile and also in Documentation/devicetree/bindings/arm/qcom.yaml. The automerge process uses git rerere (reuse recorded resolution) which staged some conflicts automatically, but ultimately failed when encountering unresolvable conflicts.
Fix: Rebase the PR branch onto the latest integration baseline (qcom-next-7.3-rc6-20261024 or later) and resolve merge conflicts manually in the Makefile and bindings YAML file.
The build failure is not caused by compilation errors in the PR code itself. The PR introduces valid device tree overlay syntax and Makefile entries. The failure occurred during the pre-compilation integration phase:
- Infrastructure issue: The automerge system cannot fetch the target branch
tech/overlay/dtbecause it doesn't exist (only the tag exists). - Integration conflicts: The PR's Makefile changes conflict with other topic branches being merged simultaneously in the integration pipeline.
No kernel compilation was attempted, so there are no compiler errors, warnings, or device tree compilation issues to report.
- Immediate: Update the PR's target branch configuration or the automerge config to use the correct tag reference
tech/overlay/dt-7.3-rc2-20261024. - Short-term: Rebase the PR onto the latest integration baseline to resolve Makefile conflicts with other topic branches.
- Verification: Re-run the build after fixing the branch reference and resolving conflicts to verify the device tree overlay compiles correctly. [/BUILD_DETAILED]