UPSTREAM: arm64: dts: qcom: talos: Add EL2 overlay for talos-evk

[LXQUALCOMM]

Add support for building an EL2 combined DTB for the talos-evk in the Qualcomm DTS Makefile.

The new talos-evk-el2.dtb is generated by combining the base talos-evk.dtb with the talos-el2.dtbo overlay, enabling EL2-specific configurations required by the platform.

CRs-Fixed: 4635242

[qlijarvis]

PR #1643 — validate-patch

PR: #1643

Verdict	Issues	Detailed Report
❌	0	Full report

Final Summary

1. Lore link present: No — UPSTREAM: prefix used but no lore.kernel.org or kernel.org link found in commit message
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: Unknown — cannot verify without lore link; UPSTREAM: prefix claims merged but no evidence provided
4. PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #1643 — arm64: dts: qcom: talos: Add EL2 overlay for talos-evk
Upstream commit: N/A — no lore.kernel.org link found
Verdict: ❌ FAIL

Commit Message

Check	Status	Note
Subject matches upstream	❌	No upstream link to compare against
Body preserves rationale	✅	Adequate description of EL2 overlay addition
Fixes tag present/correct	N/A	Not a fix; new feature
Authorship preserved	✅	From: and Signed-off-by: match
Backport note (if applicable)	N/A	Not a backport

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/Makefile	⚠️	Cannot verify against upstream — no lore link

Issues

1. Missing lore link (FAIL) — Commit uses UPSTREAM: prefix but has no Link: tag pointing to lore.kernel.org or kernel.org. According to kernel commit conventions, UPSTREAM: means "Merged into Linus's tree" and requires a verifiable upstream source.

2. Prefix inconsistency — If this patch has been posted to a mailing list but not yet merged, the correct prefix is FROMLIST:. If it's vendor-only and not intended for upstream, use QCLINUX: or PENDING:.

Verdict

Do not merge without correction. Add a Link: tag pointing to the lore.kernel.org posting or the merged kernel.org commit, or change the prefix to match the actual upstream status.

Final Summary

1. Lore link present: No — UPSTREAM: prefix used but no lore.kernel.org or kernel.org link found in commit message
2. Lore link matches PR commits: N/A — no lore link to compare against
3. Upstream patch status: Unknown — cannot verify without lore link; UPSTREAM: prefix claims merged but no evidence provided
4. PR present in qcom-next/topics: Partial — present in topics branch at 93d60582eb52e50ea11f95397a2b3633b12efa66, but missing from qcom-next

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: 8d5dbc1b17adf8fe86a41adcda686785e73f5414
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] UPSTREAM: arm64: dts: qcom: talos: Add EL2 overlay for	missing - no subject, patch-id, or full tree-content match found	present - exact patch-id match at 93d6058	present

Final Status

overall_status: PASS
present_commits: 1/1
partial_commits: 0/1
missing_commits: 0/1
topics_checked_for_commits: 1/1
final_summary: PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics

[qlijarvis]

PR #1643 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	No binding changes
dtb-check	✅	No new errors (pre-existing lemans warnings filtered)
sparse-check	⏭️	No C/H changes
check-uapi-headers	⏭️	No C/H changes
check-patch-compliance	❌	Missing Link: trailer
tag-check	✅	Valid UPSTREAM: prefix present

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1643 — UPSTREAM: arm64: dts: qcom: talos: Add EL2 overlay for talos-evk
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/31067580754

Checker	Result	Summary
checkpatch	✅	No style issues
dt-binding-check	⏭️	No binding changes
dtb-check	✅	No new errors (pre-existing lemans warnings filtered)
sparse-check	⏭️	No C/H changes
check-uapi-headers	⏭️	No C/H changes
check-patch-compliance	❌	Missing Link: trailer
tag-check	✅	Valid UPSTREAM: prefix present

❌ check-patch-compliance

Root cause: Commit is tagged UPSTREAM: but does not include a Link: trailer pointing to the upstream commit in Linus's tree.

Failure details:

Checking commit: UPSTREAM: arm64: dts: qcom: talos: Add EL2 overlay for talos-evk
No 'Link' found in commit message

Fix: Add a Link: trailer to the commit message pointing to the upstream commit in Linus's tree or a maintainer tree. The UPSTREAM: prefix indicates this patch is already merged into mainline, so the link should point to the commit in git.kernel.org or lore.kernel.org.

Steps:

git rebase -i <base_sha>   # mark commit 8d05491128a5 as 'edit'
git commit --amend         # add Link: trailer to commit body
# Example:
#   Link: https://git.kernel.org/linus/<commit-sha>
# or
#   Link: https://lore.kernel.org/r/<message-id>
git rebase --continue

Reproduce locally:

cd kernel
bash ../kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base 8d5dbc1b17adf8fe86a41adcda686785e73f5414 \
  --head 8d05491128a57620f9afee94a8de9d675dd77583

Verdict

One blocker to fix before merge: Add the missing Link: trailer to the commit message. The UPSTREAM: prefix requires a link to the upstream commit in Linus's tree or a maintainer tree. Once the link is added, the patch will be compliant.