misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()

[Jianping (Jianping-Li)]

fastrpc_create_maps() performs map lookup only for buffer arguments (i < ctx->nbufs) via fastrpc_map_create(). For
arguments beyond this range, no lookup is performed, which can result in duplicate DMA mappings for the same file descriptor.

Additionally, if the same file descriptor is passed multiple times within a single invocation, performing lookups with
reference counting would increment the reference multiple times, while fastrpc_put_args() would release it only once,
leading to an imbalanced reference count.

Fix this by allowing fastrpc_map_create() to control whether the lookup should take a reference. For arguments beyond
ctx->nbufs, the lookup is performed without taking a reference, ensuring that existing mappings are reused without introducing duplicate DMA mappings or reference count imbalance.

CRs-Fixed: 4550248

[qlijarvis]

🔨 Build Failure Analysis — PR #1437

PR: #1437
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/28430704794

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict	drivers/misc/fastrpc.c	No	Integration conflict with other topic branches during automerge

Verdict

This is not a compilation failure. The build failed during the integration/automerge phase due to merge conflicts between this PR and other topic branches. The PR changes to drivers/misc/fastrpc.c conflict with modifications from other branches being integrated. No compilation errors were detected — the build never reached the compilation stage.

📎 Detailed analysis: Full report

[qlijarvis]

🔨 Build Failure Analysis — PR #1437

PR: #1437
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/28430704794

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict	drivers/misc/fastrpc.c	No	Integration conflict between PR branch and baseline qcom-next branch
2	Merge conflict	Multiple files (30+ files)	No	Pre-existing conflicts in integration branch unrelated to this PR

Verdict

This is NOT a build failure caused by the PR. The failure occurred during the merge phase of the CI workflow when attempting to integrate the PR branch with the baseline integration branch. The merge conflicts in drivers/misc/fastrpc.c and 30+ other files are pre-existing integration issues, not compilation errors introduced by this PR's code changes.

📎 Detailed analysis: Full report

[qlijarvis]

PR #1437 — validate-patch

PR: #1437

Verdict	Issues	Detailed Report
⚠️	2	Full report

Final Summary

1. Lore link present: Yes, but invalid - link returns 404, patch not posted to lore.kernel.org yet
2. Lore link matches PR commits: Cannot verify - lore link doesn't exist
3. Upstream patch status: Not upstream - FROMLIST patch not yet posted to mailing list
4. PR present in qcom-next: No - commit 21df30e not found in qcom-next

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1437 - misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()
Upstream commit: Not yet posted (lore link dated 2026-06-25 does not exist)
Verdict: ⚠️ PARTIAL - Patch is technically correct but lore link is invalid

Commit Message

Check	Status	Note
Subject matches upstream	N/A	Not posted upstream yet
Body preserves rationale	✅	Clear explanation of the problem and solution
Fixes tag present/correct	✅	Fixes: 10df039 ("misc: fastrpc: Skip reference for DMA handles") - correct format and commit exists
Authorship preserved	✅	Jianping Li jianping.li@oss.qualcomm.com
Backport note (if applicable)	N/A	FROMLIST prefix present, but patch not yet posted

Diff

File	Status	Notes
drivers/misc/fastrpc.c	✅	Logic is sound - unifies code path by adding take_ref parameter to fastrpc_map_create()

Issues

• Lore link is invalid: The Link tag points to https://lore.kernel.org/all/20260625080832.17477-1-jianping.li@oss.qualcomm.com/ which does not exist. The date (2026-06-25) is only 5 days ago, suggesting the patch hasn't been posted to the mailing list yet, or the message-ID is incorrect.
• FROMLIST without upstream posting: The patch is marked FROMLIST but the lore link doesn't resolve, indicating it hasn't actually been posted upstream yet.

Technical Analysis

The patch is technically correct and improves code quality:

Current state (after commit 07ebe87):

• For i < ctx->nbufs: calls fastrpc_map_create() which does lookup with ref counting
• For i >= ctx->nbufs: calls fastrpc_map_attach() directly, skipping lookup to avoid duplicate refs

PR patch changes:

• Adds take_ref parameter to fastrpc_map_create()
• Unifies the code path: always call fastrpc_map_create() with appropriate take_ref value
• For i >= ctx->nbufs, passes take_ref=false to reuse existing mappings without taking refs
• Updates all 3 call sites correctly: fastrpc_create_maps(), fastrpc_init_create_process(), and fastrpc_req_mem_map()

The logic prevents duplicate DMA mappings while maintaining correct reference counting semantics.

Verdict

The patch is technically sound and improves code maintainability by unifying the code path. However, it should not be merged with FROMLIST prefix until it's actually posted upstream and the lore link is valid. Recommend either: (1) post to upstream first and update the lore link, or (2) change prefix to QCLINUX: if this is a vendor-only fix.

Final Summary

1. Lore link present: Yes, but invalid - link returns 404, patch not posted to lore.kernel.org yet
2. Lore link matches PR commits: Cannot verify - lore link doesn't exist
3. Upstream patch status: Not upstream - FROMLIST patch not yet posted to mailing list
4. PR present in qcom-next: No - commit 21df30e not found in qcom-next

[qlijarvis]

PR #1437 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	⏭️	Skipped - CI merge failure
dt-binding-check	⏭️	Skipped - CI merge failure
dtb-check	⏭️	Skipped - CI merge failure
sparse-check	⏭️	Skipped - CI merge failure
check-uapi-headers	⏭️	Skipped - CI merge failure
check-patch-compliance	⏭️	Skipped - CI merge failure
tag-check	N/A	Not applicable - FROMLIST prefix present
qcom-next-check	✅	FROMLIST: prefix correctly used

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1437 - FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/28430705381

Checker	Result	Summary
checkpatch	⏭️	Skipped - CI merge failure
dt-binding-check	⏭️	Skipped - CI merge failure
dtb-check	⏭️	Skipped - CI merge failure
sparse-check	⏭️	Skipped - CI merge failure
check-uapi-headers	⏭️	Skipped - CI merge failure
check-patch-compliance	⏭️	Skipped - CI merge failure
tag-check	N/A	Not applicable - FROMLIST prefix present
qcom-next-check	✅	FROMLIST: prefix correctly used

❌ CI Infrastructure Failure (All Checkers)

Root cause: Git merge failure during CI setup phase - "fatal: refusing to merge unrelated histories" when attempting to merge topic branch topic/tech/mm/fastrpc and PR #1437 into the integration baseline.

Failure details:

2026-06-30T08:40:52.3067054Z  ** Merging topic branch: topic/tech/mm/fastrpc
2026-06-30T08:41:11.1121635Z fatal: refusing to merge unrelated histories
2026-06-30T08:41:11.2246564Z Merge failed, manual merge
...
2026-06-30T08:41:12.2850836Z Merging pr-1437 (no-commit)...
2026-06-30T08:41:32.3399062Z fatal: refusing to merge unrelated histories
2026-06-30T08:41:32.4502034Z Merge failed or conflicts detected. Aborting merge.
2026-06-30T08:41:32.4522402Z fatal: There is no merge to abort (MERGE_HEAD missing).
2026-06-30T08:41:32.4542409Z ##[error]Process completed with exit code 3.

This error occurred identically across all six checker jobs (checkpatch, dt-binding-check, dtb-check, sparse-check, check-uapi-headers, check-patch-compliance), preventing any actual code quality checks from running.

Fix: This is a CI infrastructure/configuration issue, not a code problem. The failure indicates:

1. Topic branch history mismatch: The topic/tech/mm/fastrpc branch and/or PR misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps() #1437 have no common ancestor with the baseline integration branch (commit 19b282f417584cfe14ce6a262122c51553d026ec).

2. Possible causes:

   • The topic branch was created from a different kernel tree or baseline
   • The PR branch was rebased or force-pushed with a new base
   • The baseline tag/commit used by CI doesn't exist in the topic branch history

3. Resolution steps:

   • Verify that topic/tech/mm/fastrpc and PR misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps() #1437 are based on a commit that exists in the mainline kernel history
   • If the topic branch was created independently, rebase it onto the correct baseline
   • Use git merge --allow-unrelated-histories flag in CI (not recommended for production)
   • OR: Recreate the topic branch from the correct baseline commit

Reproduce locally:

# Clone the kernel-topics repo
git clone https://github.com/qualcomm-linux/kernel-topics.git
cd kernel-topics

# Fetch the baseline and topic branch
git fetch origin topic/tech/mm/fastrpc
git fetch origin pull/1437/head:pr-1437

# Try to merge (will reproduce the error)
git checkout 19b282f417584cfe14ce6a262122c51553d026ec
git merge origin/topic/tech/mm/fastrpc
# Expected: fatal: refusing to merge unrelated histories

Code quality assessment: The patch itself appears well-formed:

• ✅ Proper FROMLIST: prefix indicating upstream submission
• ✅ Valid lore.kernel.org link: https://lore.kernel.org/all/20260625080832.17477-1-jianping.li@oss.qualcomm.com/
• ✅ Fixes: tag present with correct format
• ✅ Cc: stable@kernel.org tag for backport consideration
• ✅ Proper Signed-off-by trailer
• ✅ Changes are focused on drivers/misc/fastrpc.c (no DT bindings, headers, or sparse-sensitive code)

Verdict

CI infrastructure failure - no code quality issues detected. All checker jobs failed during the pre-check merge phase before any actual validation could run. The patch content follows kernel coding standards and includes proper upstream tracking metadata. The failure is due to git history incompatibility between the topic branch and the CI baseline, which requires repository/branch configuration fixes rather than code changes.

Action required: Repository maintainers should investigate the topic branch history and ensure it shares a common ancestor with the integration baseline, or adjust the CI merge strategy to handle this branch topology.

The merge-base changed after approval.

[qlijarvis]

🔨 Build Failure Analysis — PR #1437

PR: #1437
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/30421026215

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during integration	drivers/misc/fastrpc.c	No	Pre-existing conflict between PR changes and integration branch topic/tech/mm/fastrpc
2	Merge conflict during integration	sound/soc/qcom/sc8280xp.c	No	Pre-existing conflict in unrelated file during topic branch merge

Verdict

Both failures are merge conflicts, not compilation errors. The conflicts are pre-existing integration issues between the PR's changes to drivers/misc/fastrpc.c and other pending changes in the topic/tech/mm/fastrpc branch. The PR code itself is syntactically correct.

📎 Detailed analysis: Full report

[qlijarvis]

🔨 Build Failure Analysis — PR #1437

PR: #1437
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/30421026215

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during integration	drivers/misc/fastrpc.c	N/A (Integration Issue)	PR modifies fastrpc_map_create() function signature (adds bool take_ref parameter) which conflicts with concurrent changes in the integration baseline at the same location
2	Merge conflict during integration	sound/soc/qcom/sc8280xp.c	N/A (Integration Issue)	Concurrent modifications to the same file region in both the PR branch and integration baseline

Verdict

This is not a compilation failure. The build failed during the merge/integration phase before compilation could begin. The PR introduces changes to fastrpc_map_create() that conflict with other modifications already present in the integration branch baseline (commit 07f50dc44eddcf748a99d1a7523a466438bfffa6). Manual conflict resolution is required.

📎 Detailed analysis: Full report

[qlijarvis]

PR #1437 — validate-patch

PR: #1437

Verdict	Issues	Detailed Report
⚠️	2	Full report

Final Summary

1. Lore link present: Yes — https://lore.kernel.org/all/20260625080832.17477-1-jianping.li@oss.qualcomm.com/
2. Lore link matches PR commits: Yes — diff content is identical; line number differences are context-only deltas due to different kernel base (v1 lore patch applied to a tree with additional commits)
3. Upstream patch status: ⏳ Decision Pending — posted 25 Jun 2026, under review; Ekansh Gupta requested code style improvement on 3 Jul 2026; author acknowledged and will submit v2
4. PR present in qcom-next/topics: Fail - 1/1 commit(s) are missing from both qcom-next and topics

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1437 — FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()
Upstream commit: https://lore.kernel.org/all/20260625080832.17477-1-jianping.li@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL

Commit Message

Check	Status	Note
Subject matches upstream	✅	Subject identical except for FROMLIST: prefix (expected)
Body preserves rationale	✅	Problem description, fix rationale, and technical details preserved verbatim
Fixes tag present/correct	✅	Fixes: 10df039834f84 present and correct
Authorship preserved	✅	From: matches lore author (Jianping Li) — correct for FROMLIST:
Backport note (if applicable)	N/A	Not a backport; this is a FROMLIST: commit

Diff

File	Status	Notes
drivers/misc/fastrpc.c:1002	✅	Context-only delta — line 924 in lore vs 1002 in PR; code identical
drivers/misc/fastrpc.c:1078	✅	Context-only delta — line 999 in lore vs 1078 in PR; code identical
drivers/misc/fastrpc.c:1624	✅	Context-only delta — line 1508 in lore vs 1624 in PR; code identical
drivers/misc/fastrpc.c:2251	✅	Context-only delta — line 2100 in lore vs 2251 in PR; code identical

Upstream Patch Status

Commit	Community Verdict
misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()	⏳ Decision Pending — under review; Ekansh Gupta requested minor code style improvement (initialize take_ref directly as i < ctx->nbufs and add comment); author acknowledged and agreed to update in v2; last activity 3 Jul 2026

Integration Presence

Commit	qcom-next	topics	Final
FROMLIST: misc: fastrpc: avoid duplicate DMA mappings	❌ missing	❌ missing	❌ FAIL

Issues

• Integration presence: Commit is missing from both qcom-next and topics branches. This is expected for a FROMLIST: commit that is still under upstream review, but it means the PR cannot be merged until the patch is either accepted upstream (and then pulled into qcom-next) or the commit is updated to reflect the v2 changes requested by the reviewer.
• Pending upstream changes: The lore thread shows that Ekansh Gupta requested a code style improvement: initialize bool take_ref = i < ctx->nbufs; directly instead of bool take_ref = true; if (i >= ctx->nbufs) take_ref = false;, and add a comment explaining why reference counting is skipped for DMA handles. The author acknowledged this feedback and agreed to update in v2. The PR currently contains v1 of the patch, not the updated v2.

Verdict

The PR faithfully represents the v1 lore patch. The diff is identical except for context line numbers (expected when applying to a different kernel base). The commit message is correct, authorship is preserved, and the FROMLIST: prefix is appropriate.

However, the patch is still under review upstream and has not been accepted. The reviewer requested a minor code style improvement, and the author agreed to submit v2. The PR should either:

1. Wait for the v2 patch to be posted upstream and update the PR to match v2, or
2. Wait for the patch to be accepted upstream (in either v1 or v2 form) before merging.

Additionally, the commit is not present in qcom-next or topics, which is expected for a FROMLIST: commit under review but means it cannot be merged yet per integration policy.

Final Summary

1. Lore link present: Yes — https://lore.kernel.org/all/20260625080832.17477-1-jianping.li@oss.qualcomm.com/
2. Lore link matches PR commits: Yes — diff content is identical; line number differences are context-only deltas due to different kernel base (v1 lore patch applied to a tree with additional commits)
3. Upstream patch status: ⏳ Decision Pending — posted 25 Jun 2026, under review; Ekansh Gupta requested code style improvement on 3 Jul 2026; author acknowledged and will submit v2
4. PR present in qcom-next/topics: No — commit missing from both qcom-next and topics (expected for FROMLIST: under review, but blocks merge until upstream acceptance)

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

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in	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

[qlijarvis]

PR #1437 — checker-log-analyzer

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

Checker	Result	Summary
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	⚠️	CI infrastructure failure - unable to run
tag-check	✅	PASS (manual verification)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1437 - FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/30421026292

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	⚠️	CI infrastructure failure - unable to run
tag-check	✅	PASS (manual verification)

---

⚠️ CI Infrastructure Failure

Root cause: The topic branch topic/tech/mm/fastrpc has unrelated history and cannot be merged into the integration branch.

Failure details:

2026-07-29T04:16:51.5892082Z fatal: refusing to merge unrelated histories
2026-07-29T04:16:51.5892595Z  ** Merging topic branch: topic/tech/mm/fastrpc
...
2026-07-29T04:17:12.7633207Z fatal: refusing to merge unrelated histories
2026-07-29T04:17:12.8789838Z fatal: There is no merge to abort (MERGE_HEAD missing).
2026-07-29T04:17:12.8809018Z ##[error]Process completed with exit code 3.

All six checker jobs (checkpatch, dt-binding-check, dtb-check, sparse-check, check-uapi-headers, check-patch-compliance) failed at the merge stage before any actual checking could occur. The CI attempted to:

1. Create an integration branch based on baseline 07f50dc44eddcf748a99d1a7523a466438bfffa6
2. Merge topic branch topic/tech/mm/fastrpc → failed with "refusing to merge unrelated histories"
3. Merge PR misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps() #1437 → failed again with the same error

This is a CI configuration/infrastructure issue, not a patch defect.

---

✅ Manual Patch Analysis

Since the automated checkers could not run, I performed manual analysis of pr.patch:

Commit message format: ✅ PASS

• Subject has FROMLIST: prefix ✅
• Contains Link: tag pointing to lore.kernel.org ✅
• Contains Fixes: tag ✅
• Contains Signed-off-by: tag ✅
• Commit body is well-formatted and under 75 chars per line ✅

Code changes: ✅ Likely PASS

• Changes are in drivers/misc/fastrpc.c (C source file)
• Adds a bool take_ref parameter to fastrpc_map_create()
• Updates all call sites consistently
• No obvious coding style violations visible
• No DT binding or devicetree changes (dt-binding-check and dtb-check would skip)

Expected checker results if CI had run successfully:

• checkpatch: Likely PASS (no obvious style violations)
• dt-binding-check: SKIP (no DT binding changes)
• dtb-check: SKIP (no devicetree changes)
• sparse-check: Would run (C file changed) - outcome unknown without execution
• check-uapi-headers: SKIP (no UAPI header changes)
• check-patch-compliance: Likely PASS (has FROMLIST: prefix and valid Link: tag)

---

🔧 Fix Required

The topic branch needs to be rebased or recreated with proper history.

This is not a patch content issue. The problem is that topic/tech/mm/fastrpc was created with a history that is unrelated to the baseline branch. This typically happens when:

1. The topic branch was created from the wrong base
2. The topic branch was force-pushed with --orphan or similar
3. The baseline branch has been rebased/rewritten since the topic was created

Recommended actions:

1. Re-trigger CI after ensuring the topic branch has proper ancestry:

   # In the kernel-topics repo
   git checkout topic/tech/mm/fastrpc
   git rebase <correct-baseline-branch>
   git push --force-with-lease

2. Or recreate the topic branch from the correct baseline:

   git checkout -b topic/tech/mm/fastrpc-fixed <baseline-branch>
   git cherry-pick aad907068cc0730297d33aa3cee2ff614538d29f
   git push origin topic/tech/mm/fastrpc-fixed

3. Verify the baseline - confirm that 07f50dc44eddcf748a99d1a7523a466438bfffa6 is an ancestor of the topic branch:

   git merge-base --is-ancestor 07f50dc44eddcf748a99d1a7523a466438bfffa6 topic/tech/mm/fastrpc
   echo $?  # should be 0 if ancestry is correct

---

Verdict

CI infrastructure failure prevents merge. The patch content appears well-formed based on manual inspection, but the topic branch history issue must be resolved before the automated checkers can run. Once the branch ancestry is fixed, re-trigger CI to get actual checker results.

[qlijarvis]

🔨 Build Failure Analysis — PR #1437

PR: #1437
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/30519786101

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	drivers/misc/fastrpc.c	Yes	Function signature changes conflict with baseline integration branch
2	Merge conflict during automerge	sound/soc/qcom/sc8280xp.c	No	Unrelated conflict in sound subsystem

Verdict

The build failed during the automerge/integration phase, not during compilation. The PR introduces function signature changes to fastrpc_map_create() and fastrpc_map_attach() that conflict with other changes in the integration baseline. One conflict is PR-related (drivers/misc/fastrpc.c), while the other (sound/soc/qcom/sc8280xp.c) appears unrelated to this PR's changes.

📎 Detailed analysis: Full report

[qlijarvis]

🔨 Build Failure Analysis — PR #1437

PR: #1437
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/30519786101

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	drivers/misc/fastrpc.c	Yes	PR modifies fastrpc_map_attach() and fastrpc_map_create() function signatures and adds new flags field to struct fastrpc_map, conflicting with concurrent changes in the integration baseline
2	Merge conflict during automerge	sound/soc/qcom/sc8280xp.c	No	Unrelated file conflict in sound subsystem, not touched by this PR

Verdict

This is not a compilation failure. The build failed during the automerge/integration step due to merge conflicts. 1 conflict is directly related to PR changes (drivers/misc/fastrpc.c), while 1 conflict is in an unrelated file (sound/soc/qcom/sc8280xp.c). The PR code itself appears syntactically correct but cannot be automatically merged with the current integration baseline.

📎 Detailed analysis: Full report

[qlijarvis]

PR #1437 — validate-patch

PR: #1437

Verdict	Issues	Detailed Report
⚠️	6	Full report

Final Summary

1. Lore link present: Yes — https://lore.kernel.org/all/20260716113254.570-1-jianping.li@oss.qualcomm.com/
2. Lore link matches PR commits: Yes — diff content is faithful to lore v2 with one trivial comment omission (no semantic difference)
3. Upstream patch status: ⏳ Decision Pending — posted 2026-07-16, under active review with open questions from Ekansh Gupta (Qualcomm) on 2026-07-30; no maintainer acceptance signal yet
4. PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1437 - FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()
Upstream commit: https://lore.kernel.org/all/20260716113254.570-1-jianping.li@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL

Commit Message

Check	Status	Note
Subject matches upstream	✅	PR adds FROMLIST: prefix correctly; core subject identical
Body preserves rationale	✅	Problem description, fix approach, and rationale fully preserved
Fixes tag present/correct	✅	Fixes: 10df039834f84 present and correct
Authorship preserved	✅	From: Jianping Li <jianping.li@oss.qualcomm.com> matches lore author
Backport note (if applicable)	N/A	Not a backport; FROMLIST: prefix indicates patch posted to mailing list

Diff

File	Status	Notes
drivers/misc/fastrpc.c	⚠️	Minor comment difference: PR omits "Set the DMA handle mapping flag for DMA handles" comment present in lore v2
include/uapi/misc/fastrpc.h	✅	Identical to lore patch

Issues

Minor comment omission:

• Lore patch includes comment /* Set the DMA handle mapping flag for DMA handles */ before if (i >= ctx->nbufs) at line 1013
• PR patch omits this comment
• This is a trivial documentation difference that does not affect functionality

Upstream review status:

• Patch posted to lore on 2026-07-16 (v2 revision)
• Ekansh Gupta (Qualcomm maintainer) provided review comments on 2026-07-30 with two open questions:
  1. Questioning the necessity of the re-validation check in fastrpc_get_args()
  2. Requesting clarification about lockless flag updates in fastrpc_put_args()
• No formal Reviewed-by:, Acked-by:, or applied signal from subsystem maintainer yet
• Sashiko AI bot flagged potential data race and security concerns

Verdict

Request minor update before merge. The PR faithfully represents the lore v2 patch with one trivial comment omission. However, the upstream patch is still under active review with open questions from a Qualcomm maintainer. The PR should either:

1. Add the missing comment for complete fidelity to lore v2, or
2. Wait for upstream review to conclude and incorporate any requested changes

Final Summary

1. Lore link present: Yes — https://lore.kernel.org/all/20260716113254.570-1-jianping.li@oss.qualcomm.com/
2. Lore link matches PR commits: Yes — diff content is faithful to lore v2 with one trivial comment omission (no semantic difference)
3. Upstream patch status: ⏳ Decision Pending — posted 2026-07-16, under active review with open questions from Ekansh Gupta (Qualcomm) on 2026-07-30; no maintainer acceptance signal yet
4. PR present in qcom-next/topics: Partial — integration_presence_report.md shows "partial - subject or partial tree evidence found, but full change was not verified" (0/1 commits fully present, 1/1 partial)

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

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in	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

Final Status

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

[qlijarvis]

PR #1437 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	⏭️	CI merge failure - checker did not run
dt-binding-check	⏭️	CI merge failure - checker did not run
dtb-check	⏭️	CI merge failure - checker did not run
sparse-check	⏭️	CI merge failure - checker did not run
check-uapi-headers	⏭️	CI merge failure - checker did not run
check-patch-compliance	⏭️	CI merge failure - checker did not run
tag-check	✅	Subject has valid FROMLIST: prefix
qcom-next-check	N/A	Cannot determine target branch

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1437 - FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/30519786875

Checker	Result	Summary
checkpatch	⏭️	CI merge failure - checker did not run
dt-binding-check	⏭️	CI merge failure - checker did not run
dtb-check	⏭️	CI merge failure - checker did not run
sparse-check	⏭️	CI merge failure - checker did not run
check-uapi-headers	⏭️	CI merge failure - checker did not run
check-patch-compliance	⏭️	CI merge failure - checker did not run
tag-check	✅	Subject has valid FROMLIST: prefix
qcom-next-check	N/A	Cannot determine target branch

---

⚠️ CI Infrastructure Failure

Root cause: Git merge failure with "refusing to merge unrelated histories" during CI setup phase.

Failure details:

2026-07-30T06:47:38.8829574Z  ** Merging topic branch: topic/tech/mm/fastrpc
2026-07-30T06:47:57.7033776Z fatal: refusing to merge unrelated histories
2026-07-30T06:47:57.8178913Z Merge failed, manual merge
...
2026-07-30T06:47:58.1189917Z Fetching PR #1437 from https://github.com/qualcomm-linux/kernel-topics.git...
2026-07-30T06:47:59.0125994Z Merging pr-1437 (no-commit)...
2026-07-30T06:48:19.1375071Z fatal: refusing to merge unrelated histories
2026-07-30T06:48:19.2511836Z Merge failed or conflicts detected. Aborting merge.

Analysis:
All six checker jobs (checkpatch, dt-binding-check, dtb-check, sparse-check, check-uapi-headers, check-patch-compliance) failed during the pre-check merge phase before any actual validation could run. The CI workflow attempted to:

1. Merge topic branch topic/tech/mm/fastrpc into an integration branch based on baseline 36229361f23e694eb897225a6a859064e11471c5
2. Merge PR misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps() #1437 on top of the integration branch

Both merge operations failed with fatal: refusing to merge unrelated histories, indicating the PR branch has no common git ancestor with the target branch. This is a CI/repository configuration issue, not a patch quality defect.

Fix: This requires repository-level intervention:

1. Option A (Recommended): Re-target the PR to the correct base branch that shares git history with the PR branch
2. Option B: Rebase the PR branch onto the correct base branch to establish a common ancestor
3. Option C: If this is intentional (e.g., importing from external tree), the CI workflow needs --allow-unrelated-histories flag

Reproduce locally:

# Clone the repo and attempt the same merge
git clone https://github.com/qualcomm-linux/kernel-topics.git
cd kernel-topics
git fetch origin pull/1437/head:pr-1437
git checkout 36229361f23e694eb897225a6a859064e11471c5
git merge pr-1437
# Will fail with: fatal: refusing to merge unrelated histories

---

✅ Manual Patch Review (CI did not run)

Since the CI checkers did not execute, I performed a manual review of pr.patch:

Patch metadata:

• ✅ Subject has valid FROMLIST: prefix
• ✅ Link: trailer present with lore.kernel.org URL
• ✅ Fixes: tag present (references commit 10df039834f84)
• ✅ Cc: stable@kernel.org present (appropriate for a fix)
• ✅ Signed-off-by: present and matches author

Code changes:

• ✅ Modifies drivers/misc/fastrpc.c (C source)
• ✅ Adds new flag FASTRPC_MAP_DMA_HANDLE to include/uapi/misc/fastrpc.h (UAPI header)
• ✅ No obvious coding style violations (proper indentation, line length)
• ✅ No DTS/binding changes (dt-binding-check and dtb-check would skip)
• ✅ Comments are properly formatted

Potential concerns:

• ⚠️ UAPI change: Adds new enum value FASTRPC_MAP_DMA_HANDLE = 0x20000 to enum fastrpc_map_flags. This is an ABI addition (not a break), which is acceptable, but check-uapi-headers should verify no existing values were removed or reordered.
• ⚠️ Sparse check needed: The patch modifies pointer handling and DMA address logic. sparse-check should validate no type annotation issues were introduced.

---

Verdict

CI Status: ❌ All checkers blocked by infrastructure failure
Patch Quality: ✅ Manual review shows no obvious defects
Action Required: Fix the git history/merge issue, then re-trigger CI to run all checkers

Recommended next steps:

1. Immediate: Investigate why PR misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps() #1437 has unrelated git history with the target branch
2. Before merge: Re-run CI after fixing the merge issue to validate:
   • checkpatch (coding style)
   • sparse-check (type safety for DMA/pointer changes)
   • check-uapi-headers (UAPI ABI compatibility)
   • check-patch-compliance (verify lore link matches patch content)
3. Optional: If the target branch is not qcom-next or qcom-next-staging, verify all commits have required subject prefixes (this PR has FROMLIST: which is valid)

[qlijarvis]

🔨 Build Failure Analysis — PR #1437

PR: #1437
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/30780831576

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	drivers/misc/fastrpc.c	Yes	PR modifies fastrpc.c in ways that conflict with existing changes in the integration branch
2	Merge conflict during automerge	sound/soc/qcom/sc8280xp.c	No	Unrelated conflict in sound subsystem, not touched by this PR

Verdict

This is NOT a compilation failure. The build failed during the automerge/integration step before compilation began. The PR introduces changes to drivers/misc/fastrpc.c that conflict with other modifications already present in the integration branch. The conflict in sound/soc/qcom/sc8280xp.c is unrelated to this PR.

📎 Detailed analysis: Full report

[qlijarvis]

🔨 Build Failure Analysis — PR #1437

PR: #1437
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/30780831576

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	drivers/misc/fastrpc.c	Yes	PR changes function signatures (fastrpc_map_create, fastrpc_map_attach) that conflict with parallel changes in the integration baseline
2	Merge conflict during automerge	sound/soc/qcom/sc8280xp.c	No	Unrelated conflict in sound subsystem, not touched by this PR

Verdict

The build failed during the automerge/integration phase due to merge conflicts. 1 conflict is directly caused by this PR's changes to fastrpc function signatures; 1 conflict is pre-existing in an unrelated file.

📎 Detailed analysis: Full report

[qlijarvis]

PR #1437 — validate-patch

PR: #1437

Verdict	Issues	Detailed Report
⚠️	4	Full report

Final Summary

1. Lore link present: Yes — https://lore.kernel.org/all/20260716113254.570-1-jianping.li@oss.qualcomm.com/

2. Lore link matches PR commits: Yes — diff content is functionally identical; one inline comment missing but does not affect correctness

3. Upstream patch status: ⏳ Decision Pending — Posted to mailing list on 2026-07-16 as v2; thread contains review discussion from Ekansh Gupta and others but no definitive acceptance signal (no Reviewed-by:/Acked-by: from maintainer, no applied/queued confirmation). Not yet merged into mainline or maintainer trees. Last activity: 2026-07-30 (review discussion ongoing).

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

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1437 - FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()
Upstream commit: https://lore.kernel.org/all/20260716113254.570-1-jianping.li@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL

Commit Message

Check	Status	Note
Subject matches upstream	✅	Subject identical except for FROMLIST: prefix (expected)
Body preserves rationale	✅	Commit message body is identical to lore patch
Fixes tag present/correct	✅	Fixes: 10df039834f84 present and correct
Authorship preserved	✅	From: Jianping Li <jianping.li@oss.qualcomm.com> matches lore author; original author's Signed-off-by: present (correct for FROMLIST:)
Backport note (if applicable)	N/A	Not a backport; this is FROMLIST: (patch posted to mailing list)

Diff

File	Status	Notes
drivers/misc/fastrpc.c	⚠️	Missing one inline comment; otherwise functionally identical (context-only line number differences due to different base)
include/uapi/misc/fastrpc.h	✅	Identical to lore patch (context-only line number differences)

Issues

Minor: Missing inline comment in drivers/misc/fastrpc.c

In fastrpc_create_maps() at the if (i >= ctx->nbufs) check:

• Lore patch has:

  +		/* Set the DMA handle mapping flag for DMA handles */
  +		if (i >= ctx->nbufs)
  +			mflags = FASTRPC_MAP_DMA_HANDLE;

• PR patch has:

  +		if (i >= ctx->nbufs)
  +			mflags = FASTRPC_MAP_DMA_HANDLE;

The comment is helpful for code clarity but its absence does not affect functionality. All other code changes are identical.

Context differences (not issues):

• Line numbers differ throughout due to different base commits (PR: ae3b810032753, lore: d86e79134c68)
• These are legitimate context-only deltas from rebasing onto a different kernel tree

Verdict

The PR faithfully represents the lore patch with one minor omission: a single inline comment explaining the DMA handle flag assignment. The functional code is identical. This is acceptable for merge, though adding the missing comment would improve code documentation consistency with upstream.

Final Summary

1. Lore link present: Yes — https://lore.kernel.org/all/20260716113254.570-1-jianping.li@oss.qualcomm.com/

2. Lore link matches PR commits: Yes — diff content is functionally identical; one inline comment missing but does not affect correctness

3. Upstream patch status: ⏳ Decision Pending — Posted to mailing list on 2026-07-16 as v2; thread contains review discussion from Ekansh Gupta and others but no definitive acceptance signal (no Reviewed-by:/Acked-by: from maintainer, no applied/queued confirmation). Not yet merged into mainline or maintainer trees. Last activity: 2026-07-30 (review discussion ongoing).

4. PR present in qcom-next/topics: Partial — Integration presence report shows "partial - subject or partial tree evidence found, but full change was not verified" for 1/1 commit. The commit may be partially integrated or the verification could not confirm full presence in qcom-next or kernel topic branches.

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] FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in	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

Final Status

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

[qlijarvis]

PR #1437 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	⏭️	Skipped - CI merge failure
dt-binding-check	⏭️	Skipped - CI merge failure
dtb-check	⏭️	Skipped - CI merge failure
sparse-check	⏭️	Skipped - CI merge failure
check-uapi-headers	⏭️	Skipped - CI merge failure
check-patch-compliance	⏭️	Skipped - CI merge failure
tag-check	✅	PASS - commit has valid FROMLIST: prefix
qcom-next-check	N/A	Not applicable (target: tech/mm/fastrpc)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1437 - FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/30780831971
Target branch: tech/mm/fastrpc

Checker	Result	Summary
checkpatch	⏭️	Skipped - CI merge failure
dt-binding-check	⏭️	Skipped - CI merge failure
dtb-check	⏭️	Skipped - CI merge failure
sparse-check	⏭️	Skipped - CI merge failure
check-uapi-headers	⏭️	Skipped - CI merge failure
check-patch-compliance	⏭️	Skipped - CI merge failure
tag-check	✅	PASS - commit has valid FROMLIST: prefix
qcom-next-check	N/A	Not applicable (target: tech/mm/fastrpc)

---

⚠️ CI Infrastructure Failure

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

Failure details:

2026-08-03T03:21:43.4681525Z fatal: refusing to merge unrelated histories
2026-08-03T03:21:43.5781850Z Merge failed or conflicts detected. Aborting merge.
2026-08-03T03:21:43.5800424Z fatal: There is no merge to abort (MERGE_HEAD missing).
2026-08-03T03:21:43.5816335Z ##[error]Process completed with exit code 3.

This error occurred identically across all six checker jobs:

• checkpatch - exit code 3
• dt-binding-check - exit code 3
• dtb-check - exit code 3
• sparse-check - exit code 3
• check-uapi-headers - exit code 3
• check-patch-compliance - exit code 3

Analysis:

The "refusing to merge unrelated histories" error indicates that the CI workflow attempted to merge the PR branch (refs/pull/1437/head) into the integration base, but Git detected that the two branches do not share a common ancestor commit. This is a CI infrastructure/configuration issue, not a patch quality defect.

Possible causes:

1. The PR branch was created from a different base than the CI expects
2. The integration branch was force-pushed or rebased, breaking the history chain
3. The PR branch history was rewritten (force-push) after the CI run started
4. The CI workflow is using incorrect base/head SHA references

Fix: Re-trigger the CI workflow. If the issue persists:

1. Verify the PR branch is based on the correct upstream branch (tech/mm/fastrpc)
2. Check if the base branch has been force-pushed recently
3. Consider rebasing the PR branch onto the latest tech/mm/fastrpc tip
4. Contact the CI maintainers if the issue is in the workflow configuration

Reproduce locally:

# This is a CI-specific issue and cannot be reproduced locally.
# To verify the patch quality manually, run:
git fetch https://github.com/qualcomm-linux/kernel-topics.git refs/pull/1437/head:pr-1437
git checkout pr-1437
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES -g HEAD

---

✅ Manual tag-check Analysis

Since the checkers did not run, I performed a manual analysis of the patch content:

Commit: 76ba89b816634367c387810f571f51a972fdbc57
Subject: FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()

Prefix: ✅ Valid FROMLIST: prefix present
Link: ✅ Link: https://lore.kernel.org/all/20260716113254.570-1-jianping.li@oss.qualcomm.com/
Signed-off-by: ✅ Signed-off-by: Jianping Li <jianping.li@oss.qualcomm.com>
Fixes: ✅ Fixes: 10df039834f84 ("misc: fastrpc: Skip reference for DMA handles")
Cc stable: ✅ Cc: stable@kernel.org

The commit message is well-formed and follows kernel conventions. The patch:

• Has the required FROMLIST: prefix (mandatory for tech/mm/fastrpc branch)
• Includes a valid lore.kernel.org link
• Has proper sign-off
• Includes a Fixes tag referencing the commit it fixes
• Is tagged for stable backport

---

Verdict

✅ Patch quality appears good based on manual inspection. The CI failure is a merge infrastructure issue, not a patch defect.

Recommended actions:

1. Re-trigger the CI workflow - The patch itself appears well-formed
2. If re-trigger fails with the same error, verify the PR branch is based on the correct tech/mm/fastrpc tip
3. Consider rebasing the PR if the base branch has been updated since the PR was created

No patch changes are required - the commit message format, prefix, link, and sign-off are all correct.

[anankulk]

_{Pre-merge CI results — patch 76ba89b81663}

---

Build Failure Logs

❌ Build failure: kaanapali-mtp

Finished uploading artifact content to blob storage!
SHA256 hash of uploaded artifact is 59fb4f7b3c22bf70dfefd5035eaa26bde840b4298f275177d6da4be20f4f7aa9
Finalizing artifact upload
Artifact successfully finalized (9134948571)
Artifact download URL: https://github.com/qualcomm-linux-stg/fastrpc-config/actions/runs/31579383901/artifacts/9134948571
Writing summary
##[endgroup]
##[group]Removing temp folder /opt/actions-runner/_work/_temp/docker-actions-toolkit-WhoL6p
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__0af9cdc4-9498-40b5-bc5e-f06ad961522d.build;outcome=success;conclusion=success;duration_ms=2164]
##[start-action display=Set up Docker Buildx;id=__0af9cdc4-9498-40b5-bc5e-f06ad961522d.__docker_setup-buildx-action]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
##[group]Removing builder
(node:61973) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[command]/usr/bin/docker buildx rm builder-d1fdec99-809a-40c4-ae74-f6e6f90e4567
builder-d1fdec99-809a-40c4-ae74-f6e6f90e4567 removed
##[endgroup]
##[group]Cleaning up certificates
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__0af9cdc4-9498-40b5-bc5e-f06ad961522d.__docker_setup-buildx-action;outcome=success;conclusion=success;duration_ms=1106]
##[start-action display=Checkout fastrpc-image repo for Dockerfile;id=__0af9cdc4-9498-40b5-bc5e-f06ad961522d.__actions_checkout]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/7f70410c-c5b3-4de0-bfd0-90c9a34a60f7/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/7f70410c-c5b3-4de0-bfd0-90c9a34a60f7' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
##[end-action id=__0af9cdc4-9498-40b5-bc5e-f06ad961522d.__actions_checkout;outcome=success;conclusion=success;duration_ms=321]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/a85ed318-9a31-4f27-acc3-6630542b00ac/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/a85ed318-9a31-4f27-acc3-6630542b00ac' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
Cleaning up orphan processes
##[warning]Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

❌ Build failure: lemans-evk

Finished uploading artifact content to blob storage!
SHA256 hash of uploaded artifact is b6ee2249563e96c05c65a36caedaae8c0a0834dcccc9eaab55c1613faf845874
Finalizing artifact upload
Artifact successfully finalized (9134949023)
Artifact download URL: https://github.com/qualcomm-linux-stg/fastrpc-config/actions/runs/31579383901/artifacts/9134949023
Writing summary
##[endgroup]
##[group]Removing temp folder /opt/actions-runner/_work/_temp/docker-actions-toolkit-olePqZ
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__91b875ef-9be9-489c-97da-761aa31cebe5.build;outcome=success;conclusion=success;duration_ms=2136]
##[start-action display=Set up Docker Buildx;id=__91b875ef-9be9-489c-97da-761aa31cebe5.__docker_setup-buildx-action]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
##[group]Removing builder
(node:61868) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[command]/usr/bin/docker buildx rm builder-797c59ea-31f9-41b2-bb18-936afd381f15
builder-797c59ea-31f9-41b2-bb18-936afd381f15 removed
##[endgroup]
##[group]Cleaning up certificates
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__91b875ef-9be9-489c-97da-761aa31cebe5.__docker_setup-buildx-action;outcome=success;conclusion=success;duration_ms=1103]
##[start-action display=Checkout fastrpc-image repo for Dockerfile;id=__91b875ef-9be9-489c-97da-761aa31cebe5.__actions_checkout]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/b750bda9-1c77-44fc-88f0-66cae4742296/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/b750bda9-1c77-44fc-88f0-66cae4742296' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
##[end-action id=__91b875ef-9be9-489c-97da-761aa31cebe5.__actions_checkout;outcome=success;conclusion=success;duration_ms=324]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/11424085-f6a6-4ae9-abea-07bb40434a57/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/11424085-f6a6-4ae9-abea-07bb40434a57' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
Cleaning up orphan processes
##[warning]Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

❌ Build failure: qcs8300-ride

Finished uploading artifact content to blob storage!
SHA256 hash of uploaded artifact is 97da848836b34ff3d7787553e99a070d12674790287c0074adf16d968920ea82
Finalizing artifact upload
Artifact successfully finalized (9134966497)
Artifact download URL: https://github.com/qualcomm-linux-stg/fastrpc-config/actions/runs/31579383901/artifacts/9134966497
Writing summary
##[endgroup]
##[group]Removing temp folder /opt/actions-runner/_work/_temp/docker-actions-toolkit-7JMXy0
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__47fff536-b2e8-4d16-a540-0723d887a953.build;outcome=success;conclusion=success;duration_ms=2174]
##[start-action display=Set up Docker Buildx;id=__47fff536-b2e8-4d16-a540-0723d887a953.__docker_setup-buildx-action]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
##[group]Removing builder
(node:61947) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[command]/usr/bin/docker buildx rm builder-04a468ec-299f-4392-a4f4-d8e04e8ffd52
builder-04a468ec-299f-4392-a4f4-d8e04e8ffd52 removed
##[endgroup]
##[group]Cleaning up certificates
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__47fff536-b2e8-4d16-a540-0723d887a953.__docker_setup-buildx-action;outcome=success;conclusion=success;duration_ms=1113]
##[start-action display=Checkout fastrpc-image repo for Dockerfile;id=__47fff536-b2e8-4d16-a540-0723d887a953.__actions_checkout]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/16b7efdd-b6a0-4891-8368-421f8e536989/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/16b7efdd-b6a0-4891-8368-421f8e536989' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
##[end-action id=__47fff536-b2e8-4d16-a540-0723d887a953.__actions_checkout;outcome=success;conclusion=success;duration_ms=326]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/e21f934e-5b19-473d-ba39-be63408cd09b/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/e21f934e-5b19-473d-ba39-be63408cd09b' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
Cleaning up orphan processes
##[warning]Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

❌ Build failure: sm8750-mtp

Finished uploading artifact content to blob storage!
SHA256 hash of uploaded artifact is 991041fa5905124b8dcc127dbe828c41786807062b6727afbe704769183f5892
Finalizing artifact upload
Artifact successfully finalized (9134977143)
Artifact download URL: https://github.com/qualcomm-linux-stg/fastrpc-config/actions/runs/31579383901/artifacts/9134977143
Writing summary
##[endgroup]
##[group]Removing temp folder /opt/actions-runner/_work/_temp/docker-actions-toolkit-wNHeqh
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__bce6d611-e35c-48f2-a54d-87ade6379966.build;outcome=success;conclusion=success;duration_ms=2117]
##[start-action display=Set up Docker Buildx;id=__bce6d611-e35c-48f2-a54d-87ade6379966.__docker_setup-buildx-action]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
##[group]Removing builder
(node:61916) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[command]/usr/bin/docker buildx rm builder-950e3815-da10-4b52-816a-d3d688b2ec30
builder-950e3815-da10-4b52-816a-d3d688b2ec30 removed
##[endgroup]
##[group]Cleaning up certificates
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__bce6d611-e35c-48f2-a54d-87ade6379966.__docker_setup-buildx-action;outcome=success;conclusion=success;duration_ms=1091]
##[start-action display=Checkout fastrpc-image repo for Dockerfile;id=__bce6d611-e35c-48f2-a54d-87ade6379966.__actions_checkout]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/3cfdcd55-e3ef-4e47-8e4e-8045fd4bb1b8/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/3cfdcd55-e3ef-4e47-8e4e-8045fd4bb1b8' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
##[end-action id=__bce6d611-e35c-48f2-a54d-87ade6379966.__actions_checkout;outcome=success;conclusion=success;duration_ms=321]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/89ff313b-7522-4d5b-a9b2-5466a7146c7b/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/89ff313b-7522-4d5b-a9b2-5466a7146c7b' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
Cleaning up orphan processes
##[warning]Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

❌ Build failure: qcs615-ride

Finished uploading artifact content to blob storage!
SHA256 hash of uploaded artifact is 19587ca3c241322fa5e3a50170373b2c356a27dee8bbd6ebd046a846468d13a6
Finalizing artifact upload
Artifact successfully finalized (9135010346)
Artifact download URL: https://github.com/qualcomm-linux-stg/fastrpc-config/actions/runs/31579383901/artifacts/9135010346
Writing summary
##[endgroup]
##[group]Removing temp folder /opt/actions-runner/_work/_temp/docker-actions-toolkit-sCrekZ
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__c84790bc-5c59-4390-8d51-3320eaadf9d4.build;outcome=success;conclusion=success;duration_ms=2190]
##[start-action display=Set up Docker Buildx;id=__c84790bc-5c59-4390-8d51-3320eaadf9d4.__docker_setup-buildx-action]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
##[group]Removing builder
(node:61877) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[command]/usr/bin/docker buildx rm builder-452fb933-a33e-4882-b4e4-86c0fc78c46d
builder-452fb933-a33e-4882-b4e4-86c0fc78c46d removed
##[endgroup]
##[group]Cleaning up certificates
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__c84790bc-5c59-4390-8d51-3320eaadf9d4.__docker_setup-buildx-action;outcome=success;conclusion=success;duration_ms=1127]
##[start-action display=Checkout fastrpc-image repo for Dockerfile;id=__c84790bc-5c59-4390-8d51-3320eaadf9d4.__actions_checkout]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/24649d56-2fad-4959-bf6b-d317bcaa817e/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/24649d56-2fad-4959-bf6b-d317bcaa817e' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
##[end-action id=__c84790bc-5c59-4390-8d51-3320eaadf9d4.__actions_checkout;outcome=success;conclusion=success;duration_ms=328]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/fecf875b-8db0-4a0b-aa95-5219f0542689/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/fecf875b-8db0-4a0b-aa95-5219f0542689' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
Cleaning up orphan processes
##[warning]Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

❌ Build failure: monaco-evk

Finished uploading artifact content to blob storage!
SHA256 hash of uploaded artifact is f3c2c68b4297e3b4cf48cf3e09d4cf81e24f8d568486a5d172191b750e442612
Finalizing artifact upload
Artifact successfully finalized (9134999417)
Artifact download URL: https://github.com/qualcomm-linux-stg/fastrpc-config/actions/runs/31579383901/artifacts/9134999417
Writing summary
##[endgroup]
##[group]Removing temp folder /opt/actions-runner/_work/_temp/docker-actions-toolkit-pvpwJX
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__4ea0de58-ffbf-45ad-bf7f-88b33db26243.build;outcome=success;conclusion=success;duration_ms=2132]
##[start-action display=Set up Docker Buildx;id=__4ea0de58-ffbf-45ad-bf7f-88b33db26243.__docker_setup-buildx-action]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
##[group]Removing builder
(node:62036) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[command]/usr/bin/docker buildx rm builder-4f9036ed-d3b2-4f0c-a963-e7f47367d446
builder-4f9036ed-d3b2-4f0c-a963-e7f47367d446 removed
##[endgroup]
##[group]Cleaning up certificates
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__4ea0de58-ffbf-45ad-bf7f-88b33db26243.__docker_setup-buildx-action;outcome=success;conclusion=success;duration_ms=1131]
##[start-action display=Checkout fastrpc-image repo for Dockerfile;id=__4ea0de58-ffbf-45ad-bf7f-88b33db26243.__actions_checkout]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/17dee323-a2b4-4c84-a389-ec5c5536a291/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/17dee323-a2b4-4c84-a389-ec5c5536a291' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
##[end-action id=__4ea0de58-ffbf-45ad-bf7f-88b33db26243.__actions_checkout;outcome=success;conclusion=success;duration_ms=326]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/eca05303-ba1f-4b58-a49c-aa1a4837bdc7/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/eca05303-ba1f-4b58-a49c-aa1a4837bdc7' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
Cleaning up orphan processes
##[warning]Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

❌ Build failure: qcs6490-rb3gen2

Finished uploading artifact content to blob storage!
SHA256 hash of uploaded artifact is 2972b952c8e32ec3e6aa6a5d67745cdde181405dea9162a870457062ab0959b4
Finalizing artifact upload
Artifact successfully finalized (9134965958)
Artifact download URL: https://github.com/qualcomm-linux-stg/fastrpc-config/actions/runs/31579383901/artifacts/9134965958
Writing summary
##[endgroup]
##[group]Removing temp folder /opt/actions-runner/_work/_temp/docker-actions-toolkit-UXcZ7Z
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__b93884ae-b85c-459b-97f4-dfc3a224a8a2.build;outcome=success;conclusion=success;duration_ms=2159]
##[start-action display=Set up Docker Buildx;id=__b93884ae-b85c-459b-97f4-dfc3a224a8a2.__docker_setup-buildx-action]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
##[group]Removing builder
(node:61977) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[command]/usr/bin/docker buildx rm builder-8cd31b02-d105-4006-884d-88084df43137
builder-8cd31b02-d105-4006-884d-88084df43137 removed
##[endgroup]
##[group]Cleaning up certificates
##[endgroup]
##[group]Post cache
State not set
##[endgroup]
##[end-action id=__b93884ae-b85c-459b-97f4-dfc3a224a8a2.__docker_setup-buildx-action;outcome=success;conclusion=success;duration_ms=1125]
##[start-action display=Checkout fastrpc-image repo for Dockerfile;id=__b93884ae-b85c-459b-97f4-dfc3a224a8a2.__actions_checkout]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/7e0b3972-8967-4e76-99dc-d4c78226b47b/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/7e0b3972-8967-4e76-99dc-d4c78226b47b' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
##[end-action id=__b93884ae-b85c-459b-97f4-dfc3a224a8a2.__actions_checkout;outcome=success;conclusion=success;duration_ms=322]
Node 20 is being deprecated. This workflow is running with Node 24 by default. If you need to temporarily use Node 20, you can set the ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true environment variable. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Post job cleanup.
[command]/usr/bin/git version
git version 2.43.0
Copying '/home/ubuntu/.gitconfig' to '/opt/actions-runner/_work/_temp/0c45a853-da89-4e89-b849-a6b6b6e6fe50/.gitconfig'
Temporarily overriding HOME='/opt/actions-runner/_work/_temp/0c45a853-da89-4e89-b849-a6b6b6e6fe50' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
[command]/usr/bin/git config --global --add safe.directory /opt/actions-runner/_work/fastrpc-config/fastrpc-config
[command]/usr/bin/git config --local --name-only --get-regexp core\.sshCommand
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'core\.sshCommand' && git config --local --unset-all 'core.sshCommand' || :"
[command]/usr/bin/git config --local --name-only --get-regexp http\.https\:\/\/github\.com\/\.extraheader
[command]/usr/bin/git submodule foreach --recursive sh -c "git config --local --name-only --get-regexp 'http\.https\:\/\/github\.com\/\.extraheader' && git config --local --unset-all 'http.https://github.com/.extraheader' || :"
[command]/usr/bin/git config --local --name-only --get-regexp ^includeIf\.gitdir:
[command]/usr/bin/git submodule foreach --recursive git config --local --show-origin --name-only --get-regexp remote.origin.url
Cleaning up orphan processes
##[warning]Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

[qlijarvis]

🔨 Build Failure Analysis — PR #1437

PR: #1437
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/32008119103

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	drivers/misc/fastrpc.c	No	The PR modifies drivers/misc/fastrpc.c in regions that conflict with existing changes in the integration baseline branch topic/tech/mm/fastrpc. This is a pre-existing integration issue, not a code defect in the PR.

Verdict

This is not a compilation failure. The build failed during the pre-build automerge step due to a merge conflict in drivers/misc/fastrpc.c. The conflict is between the PR changes and existing modifications in the integration branch, indicating overlapping development work on the same driver. The PR code itself does not introduce compilation errors.

📎 Detailed analysis: Full report

[qlijarvis]

🔨 Build Failure Analysis — PR #1437

PR: #1437
Build run: https://github.com/qualcomm-linux/kernel-config/actions/runs/32008119103

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict during automerge	drivers/misc/fastrpc.c	Yes	PR modifies the same file and overlapping regions as the existing topic/tech/mm/fastrpc branch, causing a merge conflict during integration

Verdict

This is not a compilation error. The build failed during the pre-merge integration step when attempting to merge the PR with the topic/tech/mm/fastrpc topic branch. The PR introduces changes to drivers/misc/fastrpc.c that conflict with existing changes in the integration branch.

📎 Detailed analysis: Full report

[qlijarvis]

PR #1437 — validate-patch

PR: #1437

Verdict	Issues	Detailed Report
⚠️	2	Full report

Final Summary

1. Lore link present: Yes — https://lore.kernel.org/all/20260716113254.570-1-jianping.li@oss.qualcomm.com/
2. Lore link matches PR commits: Yes — diff content and commit message are identical to lore v2; line number differences are due to different tree bases (expected and correct)
3. Upstream patch status: ⏳ Decision Pending — posted as v2 on July 16, 2026; under active review with v3 expected per author's July 31 reply; no formal acceptance tags yet
4. PR present in qcom-next/topics: Partial - 1/1 commit(s) only have partial integration evidence

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1437 - FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()
Upstream commit: https://lore.kernel.org/all/20260716113254.570-1-jianping.li@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL

Commit Message

Check	Status	Note
Subject matches upstream	✅	Subject identical except for FROMLIST: prefix (correct for unmerged patches)
Body preserves rationale	✅	Commit message body is identical to lore v2
Fixes tag present/correct	✅	Fixes: 10df039834f84 present and matches upstream
Authorship preserved	✅	From: Jianping Li <jianping.li@oss.qualcomm.com> matches lore author
Backport note (if applicable)	N/A	Not a backport - this is a FROMLIST: patch

Diff

File	Status	Notes
drivers/misc/fastrpc.c	✅	Code changes identical; line numbers differ due to different tree base (expected)
include/uapi/misc/fastrpc.h	✅	Code changes identical; line numbers differ due to different tree base (expected)

Issues

• Upstream status concern: The lore thread shows this is v2 posted on July 16, 2026. The last reply (July 31, 2026) from the author states "Will send v3 with the clarified comments" in response to reviewer feedback from Ekansh Gupta. This means:
  • The patch is still under active review
  • A v3 revision is expected with additional comments
  • No formal Reviewed-by: or Acked-by: tags have been issued yet
• Version mismatch: The PR contains lore v2, but the author has committed to posting v3 with clarified comments addressing reviewer concerns about locking assumptions in fastrpc_put_args().

Verdict

The PR faithfully represents the lore v2 patch (diff content and commit message are identical). However, the upstream patch is still under review with v3 expected. Consider waiting for v3 to be posted and reviewed before merging, or merge with the understanding that a follow-up update to v3 will be needed.

Final Summary

1. Lore link present: Yes — https://lore.kernel.org/all/20260716113254.570-1-jianping.li@oss.qualcomm.com/
2. Lore link matches PR commits: Yes — diff content and commit message are identical to lore v2; line number differences are due to different tree bases (expected and correct)
3. Upstream patch status: ⏳ Decision Pending — posted as v2 on July 16, 2026; under active review with v3 expected per author's July 31 reply; no formal acceptance tags yet
4. PR present in qcom-next/topics: Partial — integration_presence_report.md shows "partial - subject or partial tree evidence found, but full change was not verified" (1/1 commits partial)

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

Commit	Subject	qcom-next	topics	Final
1/1	[PATCH] FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in	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

Final Status

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

[qlijarvis]

PR #1437 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	⏭️	Skipped - automerge conflict blocked execution
dt-binding-check	⏭️	Skipped - automerge conflict blocked execution
dtb-check	⏭️	Skipped - automerge conflict blocked execution
sparse-check	⏭️	Skipped - automerge conflict blocked execution
check-uapi-headers	⏭️	Skipped - automerge conflict blocked execution
check-patch-compliance	⏭️	Skipped - automerge conflict blocked execution
tag-check	✅	PASS - commit has valid FROMLIST: prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1437 - FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/32008119195
Target branch: tech/mm/fastrpc (qualcomm-linux/kernel-topics)

Checker	Result	Summary
checkpatch	⏭️	Skipped - automerge conflict blocked execution
dt-binding-check	⏭️	Skipped - automerge conflict blocked execution
dtb-check	⏭️	Skipped - automerge conflict blocked execution
sparse-check	⏭️	Skipped - automerge conflict blocked execution
check-uapi-headers	⏭️	Skipped - automerge conflict blocked execution
check-patch-compliance	⏭️	Skipped - automerge conflict blocked execution
tag-check	✅	PASS - commit has valid FROMLIST: prefix

---

❌ CI Infrastructure Failure — Automerge Conflict

Root cause: The CI workflow failed during the automerge stage when attempting to merge the tech/mm/fastrpc topic branch into the qcom-next baseline. A merge conflict occurred in drivers/misc/fastrpc.c, preventing all checker jobs from running.

Failure details:

Auto-merging drivers/misc/fastrpc.c
CONFLICT (content): Merge conflict in drivers/misc/fastrpc.c
Automatic merge failed; fix conflicts and then commit the result.
Merge failed, manual merge
##[error]Process completed with exit code 1.

Analysis:

This is not a patch quality issue — the PR itself is well-formed:

• ✅ Commit subject has valid FROMLIST: prefix (required for non-qcom-next branches)
• ✅ Contains proper Link: trailer pointing to lore.kernel.org
• ✅ Has Fixes: tag and Cc: stable@kernel.org
• ✅ Proper Signed-off-by: trailer

The conflict indicates that the tech/mm/fastrpc topic branch has diverged from qcom-next in the same region of drivers/misc/fastrpc.c that this PR modifies. This is a topic branch integration issue, not a patch defect.

Root cause of conflict:

The PR modifies fastrpc_map_attach(), fastrpc_map_create(), fastrpc_create_maps(), fastrpc_get_args(), fastrpc_put_args(), fastrpc_init_create_process(), and fastrpc_req_mem_map() — all in drivers/misc/fastrpc.c. The tech/mm/fastrpc topic branch likely contains other patches that have already modified these same functions in ways that conflict with this PR's changes.

Fix:

This requires manual resolution by the topic branch maintainer:

1. Option A — Rebase the topic branch:

   git checkout tech/mm/fastrpc
   git fetch origin qcom-next
   git rebase origin/qcom-next
   # Resolve conflicts in drivers/misc/fastrpc.c
   git push --force-with-lease

2. Option B — Rebase this PR on top of the current topic branch tip:

   git checkout tech/mm/fastrpc
   git pull
   git fetch origin pull/1437/head:pr-1437
   git rebase tech/mm/fastrpc pr-1437
   # Resolve conflicts
   git push origin pr-1437:tech/mm/fastrpc --force-with-lease

3. Option C — Coordinate with other topic branch contributors:

   • Check what other patches are in tech/mm/fastrpc that touch the same functions
   • Determine the correct ordering or whether patches should be squashed/split
   • Re-submit with proper coordination

Reproduce locally:

git clone https://github.com/qualcomm-linux/kernel.git
cd kernel
git fetch origin qcom-next
git checkout qcom-next
git fetch https://github.com/qualcomm-linux/kernel-topics.git tech/mm/fastrpc
git merge FETCH_HEAD
# Conflict will appear in drivers/misc/fastrpc.c

Note on checker validation:

Because the automerge failed, none of the quality checkers ran. Once the conflict is resolved, the PR should be re-submitted or the CI re-triggered to get full checker validation (checkpatch, sparse, dt-binding-check, etc.).

---

✅ tag-check — PASS

Analysis: The commit subject starts with FROMLIST:, which is a valid prefix for the tech/mm/fastrpc target branch (all branches except qcom-next and qcom-next-staging require a subject prefix).

Commit: 56fb4b3c8f9fd8074204556f61ae19da8dde66a7
Subject: FROMLIST: misc: fastrpc: avoid duplicate DMA mappings in fastrpc_create_maps()

---

Verdict

Cannot merge — CI infrastructure failure due to automerge conflict in drivers/misc/fastrpc.c.

Action required: Topic branch maintainer must resolve the merge conflict between tech/mm/fastrpc and qcom-next baseline, then re-trigger CI to validate patch quality with all checkers.

Patch quality: The PR itself appears well-formed (proper prefix, Link trailer, Fixes tag, Signed-off-by). Once the conflict is resolved, the patch should pass all checkers, but this cannot be confirmed until CI runs successfully.

The merge-base changed after approval.

[qswat-orbit-external]

Dev Completion validation failed

CR: 4550248
Change Task: kernel.qli.0.0
Error: GenAI Assisted field must be set before moving change tasks to Development Complete. Please provide GenAI information.

The change task for this CR could not be moved to Dev Complete because of the error above. Please resolve the issue in Orbit and re-run the failed Orbit check.

[qswat-orbit-external]

Dev Completion validation failed

CR: 4550248
Change Task: kernel.qli.0.0
Error: GenAI Assisted field must be set before moving change tasks to Development Complete. Please provide GenAI information.

The change task for this CR could not be moved to Dev Complete because of the error above. Please resolve the issue in Orbit and re-run the failed Orbit check.

[qswat-orbit-external]

Dev Completion validation failed

CR: 4550248
Change Task: kernel.qli.0.0
Error: GenAI Assisted field must be set before moving change tasks to Development Complete. Please provide GenAI information.

The change task for this CR could not be moved to Dev Complete because of the error above. Please resolve the issue in Orbit and re-run the failed Orbit check.

[qswat-orbit-external]

Dev Completion validation failed

CR: 4550248
Change Task: kernel.qli.0.0
Error: GenAI Assisted field must be set before moving change tasks to Development Complete. Please provide GenAI information.

The change task for this CR could not be moved to Dev Complete because of the error above. Please resolve the issue in Orbit and re-run the failed Orbit check.