FROMLIST: arm64: dts: qcom: monaco-evk: Extract common EVK hardware into independent board files

[Faruque Ansari (faruque-ansari)]

Rebasing to v5 of the monaco-ac EVK series, which drops the shared
monaco-evk-common.dtsi in favor of fully independent monaco-evk.dts
and monaco-ac-evk.dts board files. Fold the dtsi's shared hardware
description directly into each board file and delete the dtsi.

[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.

[qlijarvis]

PR #1132 — validate-patch

PR: #1132

Verdict	Issues	Detailed Report
❌	0	Full report

Final Summary

1. Lore link present: Commit 1: Yes but wrong (links to cover letter, not a patch); Commit 2: Yes
2. Lore link matches PR commits: No - Commit 1 links to non-patch cover letter; Commit 2 performs different operation (reorder vs add)
3. Upstream patch status: Patches 1/3 and 3/3 ACKed and merged; Patch 2/3 reviewed but not applied; Patch 0/2 is cover letter (N/A)
4. PR present in qcom-next/topics: Partial - 1/2 commit(s) only have partial integration evidence

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #1132 - "FROMLIST: arm64: dts: qcom: monaco-evk: Extract common EVK hardware into independent board files" + "FROMLIST: arm64: dts: qcom: monaco: Align IFP mezzanine hunk position with upstream v5"

Upstream commits:

• Commit 1: https://lore.kernel.org/all/20260626111301.3479559-1-umang.chheda@oss.qualcomm.com/ (cover letter - not a patch)
• Commit 2: https://lore.kernel.org/all/20260626111301.3479559-4-umang.chheda@oss.qualcomm.com/

Verdict: ❌ FAIL

Commit Message

Check	Status	Note
Subject matches upstream	❌	Commit 1 links to cover letter (0/2), not an actual patch; Commit 2 subject describes "Align IFP mezzanine hunk position" but upstream patch adds IFP mezzanine support
Body preserves rationale	⚠️	Commit 1 describes v5 refactoring but links to cover letter; Commit 2 describes position alignment but upstream adds new functionality
Fixes tag present/correct	N/A	Not applicable - new board support
Authorship preserved	❌	PR author is Faruque Ansari but upstream author is Umang Chheda; missing Umang's Signed-off-by
Backport note (if applicable)	N/A	FROMLIST prefix used correctly

Diff

File	Status	Notes
Commit 1: monaco-ac-evk.dts, monaco-evk.dts, monaco-evk-common.dtsi	❌	Links to cover letter (message-id -1-), not an actual patch - cannot validate diff
Commit 2: Makefile	❌	PR moves existing lines; upstream adds 3 new lines for IFP mezzanine - completely different changes

Issues

Commit 1 - Critical Issues:

1. Wrong lore link: Links to cover letter 20260626111301.3479559-1- (patch 0/2) instead of an actual patch. Cover letters are not patches and cannot be cherry-picked.
2. Authorship violation: PR From: is Faruque Ansari <faruque.ansari@oss.qualcomm.com> but upstream author is Umang Chheda <umang.chheda@oss.qualcomm.com>. For FROMLIST: commits, the original author's Signed-off-by: must be present - it is missing.
3. Commit message mismatch: PR describes "Rebasing to v5 of the monaco-ac EVK series, which drops the shared monaco-evk-common.dtsi" but this describes a refactoring between v4→v5, not the actual content of any single v5 patch.

Commit 2 - Critical Issues:

1. Semantic divergence:
   • Upstream patch (message-id -4-, patch 3/3): Adds 3 new lines to create monaco-ac-evk-ifp-mezzanine combo DTB
   • PR patch: Moves existing 3 lines (the same combo) from below monaco-evk-camera-imx577 to above monaco-evk-el2 - a pure reordering operation
2. Commit message misleading: PR says "Align IFP mezzanine hunk position with upstream v5" implying the combo already exists and is being repositioned, but upstream patch 3/3 is adding it for the first time.
3. Missing prerequisite: Upstream patch 2/3 (the main monaco-ac-evk.dts board file) was not applied by the maintainer (only patches 1/3 and 3/3 were applied on Aug 31 and Sep 3, 2026 respectively). The PR assumes patch 2/3 content is already present.

Upstream Patch Status

Commit	Community Verdict
Patch 0/2 (cover letter)	N/A - cover letters are not patches
Patch 1/3 (dt-bindings)	✅ ACKed - merged as 522cffd76eb8 by Bjorn Andersson on Aug 31, 2026
Patch 2/3 (monaco-ac-evk.dts board file)	⏳ Decision Pending - Reviewed-by from Konrad Dybcio but not applied by maintainer; Sashiko AI flagged issues with GPIO expander count mismatch
Patch 3/3 (IFP mezzanine combo)	✅ ACKed - merged as 0fb8fb4e7377 by Bjorn Andersson on Sep 3, 2026

Verdict

Do not merge. This PR has multiple critical validation failures:

1. Commit 1 is not validatable - links to a cover letter instead of a patch, making it impossible to verify diff correctness against upstream.
2. Authorship violation - original author Umang Chheda's Signed-off-by: is missing from both commits.
3. Semantic divergence in Commit 2 - PR performs a reordering operation while claiming to match upstream patch that adds new content.
4. Missing dependency - Upstream patch 2/3 (main board file) was not applied by the maintainer, so the PR's assumption that the IFP mezzanine combo already exists is incorrect.

Recommendation

Reject and request rework:

1. For Commit 1: Determine which actual v5 patch(es) this commit represents. If it's meant to be patch 2/3 (monaco-ac-evk.dts), update the Link to 20260626111301.3479559-3- and ensure the diff matches. Note that patch 2/3 has not been applied upstream yet.

2. For Commit 2: This commit appears to be a local tree management operation (reordering Makefile entries) rather than a faithful representation of upstream patch 3/3. If the goal is to apply upstream patch 3/3, the commit should add the 3 lines as upstream does, not move existing lines.

3. Fix authorship: Both commits must preserve From: Umang Chheda <umang.chheda@oss.qualcomm.com> and include his Signed-off-by: trailer.

4. Verify dependency: Confirm whether patch 2/3 (main monaco-ac-evk.dts board file) should be included in this PR, since it was reviewed but not applied by the maintainer.

Final Summary

1. Lore link present: Commit 1: Yes but wrong (links to cover letter, not a patch); Commit 2: Yes
2. Lore link matches PR commits: No - Commit 1 links to non-patch cover letter; Commit 2 performs different operation (reorder vs add)
3. Upstream patch status: Patches 1/3 and 3/3 ACKed and merged; Patch 2/3 reviewed but not applied; Patch 0/2 is cover letter (N/A)
4. PR present in qcom-next/topics: Partial (1/2 commits) per integration_presence_report.md - Commit 1 has partial evidence, Commit 2 is present

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

Commit	Subject	qcom-next	topics	Final
1/2	[PATCH 1/2] FROMLIST: arm64: dts: qcom: monaco-evk: Extract common	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial
2/2	[PATCH 2/2] FROMLIST: arm64: dts: qcom: monaco: Align IFP mezzanine	present - all checked added lines are present	skipped - not checked because qcom-next already contains the change	present

Final Status

overall_status: PARTIAL
present_commits: 1/2
partial_commits: 1/2
missing_commits: 0/2
topics_checked_for_commits: 1/2
final_summary: PR present in qcom-next/topics: Partial - 1/2 commit(s) only have partial integration evidence

[qlijarvis]

PR #1132 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	⚠️	No jobs ran - merge conflict
dt-binding-check	⚠️	No jobs ran - merge conflict
dtb-check	⚠️	No jobs ran - merge conflict
sparse-check	⚠️	No jobs ran - merge conflict
check-uapi-headers	⚠️	No jobs ran - merge conflict
check-patch-compliance	⚠️	No jobs ran - merge conflict
tag-check	N/A	Cannot run - merge conflict

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1132 - FROMLIST: arm64: dts: qcom: monaco-evk: Extract common EVK hardware into independent board files
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/35198703655

Checker	Result	Summary
checkpatch	⚠️	No jobs ran - merge conflict
dt-binding-check	⚠️	No jobs ran - merge conflict
dtb-check	⚠️	No jobs ran - merge conflict
sparse-check	⚠️	No jobs ran - merge conflict
check-uapi-headers	⚠️	No jobs ran - merge conflict
check-patch-compliance	⚠️	No jobs ran - merge conflict
tag-check	N/A	Cannot run - merge conflict

---

⚠️ CI Infrastructure Issue: Merge Conflicts

Root cause: The PR cannot be merged into the target branch qcom-6.18.y due to merge conflicts, preventing all checker jobs from running.

Failure details:

Merging pr-1132 (no-commit)...
Auto-merging arch/arm64/boot/dts/qcom/Makefile
CONFLICT (modify/delete): arch/arm64/boot/dts/qcom/monaco-evk-common.dtsi deleted in pr-1132 and modified in HEAD.  Version HEAD of arch/arm64/boot/dts/qcom/monaco-evk-common.dtsi left in tree.
Auto-merging arch/arm64/boot/dts/qcom/monaco-evk.dts
CONFLICT (content): Merge conflict in arch/arm64/boot/dts/qcom/monaco-evk.dts
Automatic merge failed; fix conflicts and then commit the result.
Merge failed or conflicts detected. Aborting merge.
##[error]Process completed with exit code 3.

Analysis:

This PR attempts to delete arch/arm64/boot/dts/qcom/monaco-evk-common.dtsi and fold its contents into individual board files (monaco-evk.dts and monaco-ac-evk.dts). However, the target branch qcom-6.18.y has modifications to both:

1. monaco-evk-common.dtsi — The PR deletes this file, but the target branch has newer modifications to it (modify/delete conflict)
2. monaco-evk.dts — Both the PR and the target branch have made changes to this file (content conflict)

This indicates that the PR was created against an older version of qcom-6.18.y and needs to be rebased onto the current tip.

Fix:

The PR author needs to rebase the branch onto the latest qcom-6.18.y:

# In the PR branch
git fetch origin qcom-6.18.y
git rebase origin/qcom-6.18.y

# Resolve conflicts:
# 1. For monaco-evk-common.dtsi: Since the PR deletes it, ensure any new
#    content from the target branch is folded into the individual board files
# 2. For monaco-evk.dts: Manually merge the changes, ensuring both the PR's
#    refactoring and any new hardware additions from the target branch are preserved

git add <resolved-files>
git rebase --continue

# Force-push the rebased branch
git push --force-with-lease

Reproduce locally:

git clone https://github.com/qualcomm-linux/kernel.git
cd kernel
git checkout qcom-6.18.y
git fetch origin pull/1132/head:pr-1132
git merge pr-1132 --no-commit
# Observe the same conflicts

---

Verdict

Cannot assess patch quality — CI infrastructure blocked by merge conflicts.

The PR must be rebased onto the current qcom-6.18.y tip before any checker validation can occur. Once rebased and conflicts resolved:

1. Re-trigger the CI run
2. All six checkers will execute against the rebased commits
3. A new analysis can be performed on the actual checker results

Recommended action: Ask the PR author to rebase and resolve conflicts, then re-run CI.

[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.

[qlijarvis]

PR #1132 — validate-patch

PR: #1132

Verdict	Issues	Detailed Report
❌	0	Full report

Final Summary

1. Lore link present: Commit 1/2: Yes (but points to cover letter, not a patch) | Commit 2/2: Yes (correct message-ID)

2. Lore link matches PR commits: No — Commit 1/2 does refactoring work (delete monaco-evk-common.dtsi, modify monaco-evk.dts) not present in any lore v5 patch. Commit 2/2 content matches lore v5 3/3, but subject/body misrepresent the change as "alignment" rather than "addition".

3. Upstream patch status: ✅ ACKed — All three patches from the lore v5 series (1/3, 2/3, 3/3) have been applied upstream with maintainer approval and commit SHAs.

4. PR present in qcom-next/topics: Partial - 1/2 commit(s) only have partial integration evidence

Verdict: ❌ — click to expand

🔍 Patch Validation Report

PR: #1132
Commits: 2 commits with FROMLIST prefix
Verdict: ❌ FAIL

---

Commit 1/2: FROMLIST: arm64: dts: qcom: monaco-evk: Extract common EVK hardware into independent board files

Upstream: https://lore.kernel.org/all/20260626111301.3479559-1-umang.chheda@oss.qualcomm.com/
Verdict: ❌ FAIL

Commit Message

Check	Status	Note
Subject matches upstream	❌	Links to cover letter (0/2), not a specific patch
Body preserves rationale	⚠️	Describes refactoring work not present in any single lore patch
Fixes tag present/correct	N/A	Not applicable
Authorship preserved	❌	From: Faruque Ansari, but lore author is Umang Chheda
Original author Signed-off-by	❌	MISSING - no Signed-off-by from Umang Chheda
Submitter Signed-off-by	❌	MISSING - no Signed-off-by from Faruque Ansari

Diff

File	Status	Notes
monaco-ac-evk.dts	❌	Adds 1061 lines - no corresponding lore patch with this exact change
monaco-evk-common.dtsi	❌	Deletes file that doesn't exist in lore v5 series
monaco-evk.dts	❌	Adds 1064 lines - no corresponding lore patch with this exact change

Issues

1. Lore link points to cover letter, not a patch — The Link: tag references 20260626111301.3479559-1- which is the cover letter (0/2), not a specific patch. Cover letters are not patches and cannot be validated.

2. No matching lore patch — The lore v5 series contains:

   • [PATCH v5 1/3] dt-bindings: arm: qcom: Add monaco-ac-evk support
   • [PATCH v5 2/3] arm64: dts: qcom: monaco: Add monaco-ac EVK board (creates monaco-ac-evk.dts from scratch)
   • [PATCH v5 3/3] arm64: dts: qcom: monaco-ac-evk: Add IFP mezzanine

   None of these patches delete monaco-evk-common.dtsi or modify monaco-evk.dts. The PR commit describes "rebasing to v5" and "dropping the shared dtsi", but v5 never had a shared dtsi — that was only in v3/v4 and was already dropped before v5 was posted.

3. Authorship violation (FROMLIST) — The lore patches are authored by Umang Chheda <umang.chheda@oss.qualcomm.com>, but the PR commit is authored by Faruque Ansari <faruque.ansari@oss.qualcomm.com>. For FROMLIST commits, the original author's Signed-off-by: must be present in the commit message. It is completely missing.

4. Missing all Signed-off-by trailers — The commit has no Signed-off-by: lines at all, neither from the original author (Umang Chheda) nor from the submitter (Faruque Ansari). This violates kernel contribution guidelines.

5. Semantic mismatch — The PR commit claims to be adapting the lore v5 series, but the actual changes (deleting monaco-evk-common.dtsi, modifying monaco-evk.dts) are not present in the lore v5 series at all. This appears to be local refactoring work that should either:

   • Use a different prefix (e.g., QCLINUX: if vendor-specific), or
   • Link to the correct lore patches that correspond to the actual changes

---

Commit 2/2: FROMLIST: arm64: dts: qcom: monaco: Align IFP mezzanine hunk position with upstream v5

Upstream: https://lore.kernel.org/all/20260626111301.3479559-4-umang.chheda@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL

Commit Message

Check	Status	Note
Subject matches upstream	⚠️	Upstream: "Add IFP mezzanine"; PR: "Align IFP mezzanine hunk position"
Body preserves rationale	⚠️	Upstream adds new feature; PR describes hunk reordering
Fixes tag present/correct	N/A	Not applicable
Authorship preserved	❌	From: Faruque Ansari, but lore author is Umang Chheda
Original author Signed-off-by	❌	MISSING - no Signed-off-by from Umang Chheda
Submitter Signed-off-by	❌	MISSING - no Signed-off-by from Faruque Ansari

Diff

File	Status	Notes
arch/arm64/boot/dts/qcom/Makefile	✅	Content matches lore patch v5 3/3, but context differs

Issues

1. Authorship violation (FROMLIST) — Same issue as commit 1/2: lore author is Umang Chheda, but PR author is Faruque Ansari, and the original author's Signed-off-by: is missing.

2. Missing all Signed-off-by trailers — No Signed-off-by: lines present at all.

3. Subject/body mismatch — The lore patch subject is "Add IFP mezzanine" (adding new functionality), but the PR subject is "Align IFP mezzanine hunk position with upstream v5" (suggesting cosmetic reordering). The diff content matches the lore patch, but the commit message misrepresents the change as a reordering operation rather than a feature addition.

4. Context difference — The lore patch applies to a Makefile at line 67 (context: @@ -67,6 +67,9 @@), but the PR patch applies at line 71 (context: @@ -71,15 +71,15 @@). This suggests the PR is applying the patch to a different base that already has additional commits not present in the lore series.

---

Upstream Patch Status

Commit	Community Verdict
[PATCH v5 1/3] dt-bindings: arm: qcom: Add monaco-ac-evk support	✅ ACKed — Applied as commit 522cffd76eb8 (Acked-by: Krzysztof Kozlowski)
[PATCH v5 2/3] arm64: dts: qcom: monaco: Add monaco-ac EVK board	✅ ACKed — Applied (Reviewed-by: Konrad Dybcio)
[PATCH v5 3/3] arm64: dts: qcom: monaco-ac-evk: Add IFP mezzanine	✅ ACKed — Applied as commit 0fb8fb4e7377 (Reviewed-by: Konrad Dybcio)

Evidence: The lore thread shows "Applied, thanks!" messages from the maintainer with commit SHAs. All three patches from the v5 series have been accepted and merged.

---

Integration Presence (qcom-next/topics)

Per integration_presence_report.md:

Commit	qcom-next	topics	Final
1/2	partial	partial	partial
2/2	present	skipped	present

Overall status: PARTIAL — 1/2 commits fully present, 1/2 commits only partially present.

Note: Commit 1/2 shows "partial" evidence because it's doing refactoring work (deleting monaco-evk-common.dtsi, modifying monaco-evk.dts) that doesn't directly correspond to any single lore patch. The integration checker found subject/tree evidence but couldn't verify the full change.

---

Recommendation

DO NOT MERGE without the following corrections:

Critical issues (must fix):

1. Add Signed-off-by trailers — Both commits are missing all Signed-off-by: lines. Add:

   Signed-off-by: Umang Chheda <umang.chheda@oss.qualcomm.com>
   Signed-off-by: Faruque Ansari <faruque.ansari@oss.qualcomm.com>
   

   The original author (Umang) must be listed first, followed by the submitter (Faruque).

2. Fix commit 1/2 lore link — The Link: tag points to the cover letter, not a patch. Either:

   • Option A (recommended): Split this commit into separate commits that correspond to the actual lore patches:
     • One commit for adding monaco-ac-evk.dts (link to v5 2/3: 20260626111301.3479559-3-)
     • One commit for any local refactoring (use QCLINUX: prefix if vendor-specific)
   • Option B: If this is truly local refactoring work with no upstream equivalent, change the prefix from FROMLIST: to QCLINUX: or PENDING: and remove the lore link.

3. Fix commit 2/2 subject and body — The commit message should match the lore patch:

   • Subject: FROMLIST: arm64: dts: qcom: monaco-ac-evk: Add IFP mezzanine
   • Body: Preserve the original rationale from the lore patch (adding combined DTB support)

Advisory:

• Consider whether commit 1/2 should even exist in this PR. If the goal is to bring in the lore v5 series, the PR should contain commits that faithfully represent patches v5 1/3, 2/3, and 3/3, not a refactoring commit that deletes files the lore series never created.

---

Final Summary

1. Lore link present: Commit 1/2: Yes (but points to cover letter, not a patch) | Commit 2/2: Yes (correct message-ID)

2. Lore link matches PR commits: No — Commit 1/2 does refactoring work (delete monaco-evk-common.dtsi, modify monaco-evk.dts) not present in any lore v5 patch. Commit 2/2 content matches lore v5 3/3, but subject/body misrepresent the change as "alignment" rather than "addition".

3. Upstream patch status: ✅ ACKed — All three patches from the lore v5 series (1/3, 2/3, 3/3) have been applied upstream with maintainer approval and commit SHAs.

4. PR present in qcom-next/topics: Partial — Commit 2/2 is present; commit 1/2 shows only partial evidence (likely because it's doing work not represented in the lore series).

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

Commit	Subject	qcom-next	topics	Final
1/2	[PATCH 1/2] FROMLIST: arm64: dts: qcom: monaco-evk: Extract common	partial - subject or partial tree evidence found, but full change was not verified	partial - subject or partial tree evidence found, but full change was not verified	partial
2/2	[PATCH 2/2] FROMLIST: arm64: dts: qcom: monaco: Align IFP mezzanine	present - all checked added lines are present	skipped - not checked because qcom-next already contains the change	present

Final Status

overall_status: PARTIAL
present_commits: 1/2
partial_commits: 1/2
missing_commits: 0/2
topics_checked_for_commits: 1/2
final_summary: PR present in qcom-next/topics: Partial - 1/2 commit(s) only have partial integration evidence

[qlijarvis]

PR #1132 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	2 commits: Missing Signed-off-by (both), usb5e3 vendor undocumented (4 warnings)
dt-binding-check	⏭️	No binding changes
dtb-check	✅	All DTBs validated successfully
sparse-check	⏭️	No C/H file changes
check-uapi-headers	⏭️	No UAPI changes
check-patch-compliance	❌	Link fetch failed (commit 1), Content + Author mismatch (commit 2)
tag-check	✅	Both commits have FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1132 - Extract common EVK hardware into independent board files
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/35208390030
Target branch: qcom-6.18.y

Checker	Result	Summary
checkpatch	❌	2 commits: Missing Signed-off-by (both), usb5e3 vendor undocumented (4 warnings)
dt-binding-check	⏭️	No binding changes
dtb-check	✅	All DTBs validated successfully
sparse-check	⏭️	No C/H file changes
check-uapi-headers	⏭️	No UAPI changes
check-patch-compliance	❌	Link fetch failed (commit 1), Content + Author mismatch (commit 2)
tag-check	✅	Both commits have FROMLIST: prefix

---

❌ checkpatch

Root cause: Both commits are missing the mandatory Signed-off-by: trailer, and commit 1 uses an undocumented DT vendor prefix.

Failure details:

Commit 9c76f56 ("FROMLIST: arm64: dts: qcom: monaco-evk: Extract common EVK hardware into independent board files"):

WARNING: DT compatible string vendor "usb5e3" appears un-documented
#1013: FILE: arch/arm64/boot/dts/qcom/monaco-ac-evk.dts:1004:
+		compatible = "usb5e3,610";

WARNING: DT compatible string vendor "usb5e3" appears un-documented
#1043: FILE: arch/arm64/boot/dts/qcom/monaco-ac-evk.dts:1034:
+		compatible = "usb5e3,625";

WARNING: DT compatible string vendor "usb5e3" appears un-documented
#3209: FILE: arch/arm64/boot/dts/qcom/monaco-evk.dts:1077:
+		compatible = "usb5e3,610";

WARNING: DT compatible string vendor "usb5e3" appears un-documented
#3239: FILE: arch/arm64/boot/dts/qcom/monaco-evk.dts:1107:
+		compatible = "usb5e3,625";

ERROR: Missing Signed-off-by: line(s)

9c76f5674962 total: 1 errors, 4 warnings, 0 checks, 2187 lines checked

Commit 2a30305 ("FROMLIST: arm64: dts: qcom: monaco: Align IFP mezzanine hunk position with upstream v5"):

ERROR: Missing Signed-off-by: line(s)

2a30305be2fb total: 1 errors, 0 warnings, 0 checks, 18 lines checked

Fix:

1. Add Signed-off-by to both commits:

   git rebase -i 0ceb52911f0b
   # Mark both commits as 'edit'
   
   # For each commit:
   git commit --amend --signoff --no-edit
   git rebase --continue

2. Add usb5e3 vendor prefix (commit 1 only):

   The usb5e3 vendor (Genesys Logic) is used for USB hub devices but is not documented in vendor-prefixes.yaml. Add it:

   # Edit Documentation/devicetree/bindings/vendor-prefixes.yaml
   # Add under 'u':
   "^usb5e3,.*":
     description: Genesys Logic, Inc.

   Then amend commit 1 to include this change, or create a separate preparatory patch.

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 0ceb52911f0b..2a30305be2fb

---

❌ check-patch-compliance

Root cause: Commit 1's lore link cannot be fetched by b4 (likely a series-level link instead of patch-level), and commit 2 has both content differences and author mismatch compared to the upstream patch.

Failure details:

Commit 9c76f56:

Checking commit: FROMLIST: arm64: dts: qcom: monaco-evk: Extract common EVK hardware into independent board files
Something seems wrong with the provided link. Please verify it
Try below command to run locally-
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260626111301.3479559-1-umang.chheda@oss.qualcomm.com/

Commit 2a30305:

Checking commit: FROMLIST: arm64: dts: qcom: monaco: Align IFP mezzanine hunk position with upstream v5
Change is different from the one mentioned in Link
Author mismatch:
  Original author: Umang Chheda <umang.chheda@oss.qualcomm.com>
  Commit author : Faruque Ansari <faruque.ansari@oss.qualcomm.com>

Fix:

Commit 1 - Link issue:

The link https://lore.kernel.org/all/20260626111301.3479559-1-umang.chheda@oss.qualcomm.com/ points to the cover letter (patch 0/N) of a series, not a specific patch. The checker requires a direct patch message-ID.

Find the correct patch-level link from the series:

# Fetch the series and identify the correct patch
b4 am -o /tmp 20260626111301.3479559-1-umang.chheda@oss.qualcomm.com
# Look for the patch that matches this commit's content
# Update the Link: trailer to point to the specific patch message-ID

Likely the correct link is something like:

Link: https://lore.kernel.org/all/20260626111301.3479559-2-umang.chheda@oss.qualcomm.com/

(patch 2/N in the series, assuming patch 1/N is the cover letter or a different patch).

Commit 2 - Content + Author mismatch:

1. Author mismatch: The upstream patch author is Umang Chheda <umang.chheda@oss.qualcomm.com>, but the commit author is Faruque Ansari <faruque.ansari@oss.qualcomm.com>. Fix:

   git rebase -i 0ceb52911f0b
   # Mark commit 2a30305be2fb as 'edit'
   git commit --amend --author="Umang Chheda <umang.chheda@oss.qualcomm.com>"
   git rebase --continue

2. Content mismatch: The patch content differs from the upstream version. Fetch the upstream patch and compare:

   b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260626111301.3479559-4-umang.chheda@oss.qualcomm.com/ -o /tmp
   git format-patch -1 2a30305be2fb --stdout > /tmp/local.patch
   # Compare the diff sections

   If the difference is intentional (e.g., context adaptation for the vendor tree), document it in the commit message:

   [ Faruque: Adapted hunk position to match vendor tree context ]
   

   If the difference is unintentional, reapply the upstream patch cleanly.

Reproduce locally:

# Commit 1:
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260626111301.3479559-1-umang.chheda@oss.qualcomm.com/

# Commit 2:
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260626111301.3479559-4-umang.chheda@oss.qualcomm.com/
git format-patch -1 2a30305be2fb --stdout | diff - /tmp/upstream.mbx

---

Verdict

4 blockers must be fixed before merge:

1. ❌ Missing Signed-off-by on both commits (checkpatch ERROR) — mandatory for kernel patches
2. ❌ Undocumented vendor prefix usb5e3 (checkpatch WARNING) — add to vendor-prefixes.yaml
3. ❌ Commit 1: Invalid lore link (check-patch-compliance) — update to patch-level message-ID
4. ❌ Commit 2: Author mismatch (check-patch-compliance) — change author to Umang Chheda

Advisory:

• Commit 2 also has a content mismatch with upstream. Verify whether this is intentional adaptation or an error. If intentional, document the change in the commit message with a [ Maintainer: ... ] note.