FROMLIST: ASoC: qcom: q6apm-dai: fallback to BUFFER_BYTES_MAX without reserved memory by nandamajay · Pull Request #775 · qualcomm-linux/kernel

nandamajay · 2026-06-25T12:30:37Z

Use BUFFER_BYTES_MAX when reserved memory is not configured instead of always using reserved_buf_size, ensuring correct buffer mapping for non-reserved memory platforms.

Link: https://lore.kernel.org/all/20260624123748.502781-1-ajay.nandam@oss.qualcomm.com/
Signed-off-by: Ajay Kumar Nandam ajay.nandam@oss.qualcomm.com

CRs-Fixed: 4585950, 4586059
qli-2.0 GA Critical Fix

qlijarvis · 2026-06-25T13:31:59Z

PR #775 — validate-patch

PR: #775

Verdict	Issues	Detailed Report
⚠️	6	Full report

Final Summary

Lore link present: Yes — Link: https://lore.kernel.org/all/20260624123748.502781-1-ajay.nandam@oss.qualcomm.com/
Lore link matches PR commits: Cannot verify — network access restricted; lore.kernel.org unreachable
Upstream patch status: In review — FROMLIST: prefix indicates patch posted to mailing list but not yet merged upstream
PR present in qcom-next: Not checked — cannot access remote repositories due to network restrictions

Recommendation: The patch is technically sound and addresses a real bug (unconditional use of reserved_buf_size). To improve quality:

Add a Fixes: tag referencing the commit that introduced the bug
Expand the commit body to explain the failure scenario (what happens when reserved memory is not configured?)
Verify the lore link is accessible and matches the PR diff once network access is available

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #775 - ASoC: qcom: q6apm-dai: fallback to BUFFER_BYTES_MAX without reserved memory
Upstream commit: https://lore.kernel.org/all/20260624123748.502781-1-ajay.nandam@oss.qualcomm.com/ (cannot verify - network restricted)
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note

Subject matches upstream ⚠️ Cannot verify - lore.kernel.org unreachable; subject appears well-formed

Body preserves rationale ✅ Clear explanation of the fix: fallback to BUFFER_BYTES_MAX when reserved memory not configured

Fixes tag present/correct ❌ No Fixes: tag present; should reference the commit that introduced the bug

Authorship preserved ✅ Author: Ajay Kumar Nandam ajay.nandam@oss.qualcomm.com

Backport note (if applicable) N/A FROMLIST: prefix indicates patch is from mailing list, not yet merged

Diff

File Status Notes

sound/soc/qcom/qdsp6/q6apm-dai.c ✅ Clean conditional logic: uses has_reserved_mem flag to select buffer size

Issues

Commit Message:

Missing Fixes: tag — The patch fixes a bug where reserved_buf_size was always used regardless of whether reserved memory was configured. A Fixes: tag should reference the commit that introduced q6apm_map_memory_fixed_region() or the logic that unconditionally used reserved_buf_size.

Commit body could be more detailed — The message explains what the fix does but not why it's needed (e.g., what breaks when reserved memory is not configured? Does it cause a crash, incorrect behavior, or memory corruption?).

Code Change:

The diff is clean and follows kernel coding style

The ternary operator is properly formatted with correct indentation

Logic is sound: checks pdata->has_reserved_mem before using pdata->reserved_buf_size

Vendor Tags:

CRs-Fixed: 4583905 and qli-2.0 GA Critical Fix are present — these are Qualcomm-internal tags and acceptable for vendor trees

Verdict

Merge with minor improvement recommended. The code change is correct and well-formatted. However, the commit message should include a Fixes: tag to identify the commit that introduced the bug, and ideally provide more context about the failure scenario (e.g., crash signature, error message, or behavioral issue when reserved memory is not configured).

Final Summary

Lore link present: Yes — Link: https://lore.kernel.org/all/20260624123748.502781-1-ajay.nandam@oss.qualcomm.com/

Lore link matches PR commits: Cannot verify — network access restricted; lore.kernel.org unreachable

Upstream patch status: In review — FROMLIST: prefix indicates patch posted to mailing list but not yet merged upstream

PR present in qcom-next: Not checked — cannot access remote repositories due to network restrictions

Recommendation: The patch is technically sound and addresses a real bug (unconditional use of reserved_buf_size). To improve quality:

Add a Fixes: tag referencing the commit that introduced the bug

Expand the commit body to explain the failure scenario (what happens when reserved memory is not configured?)

Verify the lore link is accessible and matches the PR diff once network access is available

qlijarvis · 2026-06-25T13:32:01Z

PR #775 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues detected
dt-binding-check	⏭️	No changes in Documentation/devicetree/bindings
dtb-check	⏭️	No changes in arch/arm64/boot/dts/
sparse-check	✅	Passed
check-uapi-headers	✅	Passed
check-patch-compliance	❌	BLOCKER: Change differs from lore.kernel.org link
tag-check	N/A	Not applicable for qcom-6.18.y branch
qcom-next-check	⏭️	FROMLIST: prefix present; skipped for non-qcom-next branch

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #775 - FROMLIST: ASoC: qcom: q6apm-dai: fallback to BUFFER_BYTES_MAX without reserved memory
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/28170282427

Checker Result Summary

checkpatch ✅ No style issues detected

dt-binding-check ⏭️ No changes in Documentation/devicetree/bindings

dtb-check ⏭️ No changes in arch/arm64/boot/dts/

sparse-check ✅ Passed

check-uapi-headers ✅ Passed

check-patch-compliance ❌ BLOCKER: Change differs from lore.kernel.org link

tag-check N/A Not applicable for qcom-6.18.y branch

qcom-next-check ⏭️ FROMLIST: prefix present; skipped for non-qcom-next branch

❌ check-patch-compliance

Root cause: The patch content in the PR differs from the upstream patch referenced in the Link: tag.

Failure details:
2026-06-25T12:47:58.7304007Z Checking commit: FROMLIST: ASoC: qcom: q6apm-dai: fallback to BUFFER_BYTES_MAX without reserved memory
2026-06-25T12:48:04.1038593Z Change is different from the one mentioned in Link
2026-06-25T12:48:04.1102701Z 
2026-06-25T12:48:04.1104854Z Leaving /opt/actions-runner/_work/kernel-config/kernel-config/kernel
2026-06-25T12:48:04.1120038Z ##[error]Process completed with exit code 1.
The checker compared the patch in commit e0352b4b7f67 against the upstream patch at:
Link: https://lore.kernel.org/all/20260624123748.502781-1-ajay.nandam@oss.qualcomm.com/
The check-patch-compliance tool detected a mismatch between the local diff and the upstream patch. This typically occurs when:

The patch was modified after being posted to the mailing list

Additional changes were made during backport/cherry-pick

The wrong lore URL was referenced

The patch context differs due to base branch differences

Fix:
Verify the lore link is correct - Confirm the URL points to the exact patch version being applied
Compare the diffs manually:
# Fetch the upstream patch
curl -s "https://lore.kernel.org/all/20260624123748.502781-1-ajay.nandam@oss.qualcomm.com/raw" > /tmp/upstream.patch

# Compare with PR patch
git show e0352b4b7f67 > /tmp/pr.patch
diff -u /tmp/upstream.patch /tmp/pr.patch
Resolution options:
Option A (Recommended): If the patch was modified intentionally, update the commit message to explain the deviation and consider removing the Link: tag or adding a note about local modifications
Option B: If the patch should match upstream exactly, reapply the clean upstream patch:
git reset --hard c9744addfb04  # Reset to base
curl -s "https://lore.kernel.org/all/20260624123748.502781-1-ajay.nandam@oss.qualcomm.com/raw" | git am
Option C: If the lore link is incorrect, update the Link: tag to point to the correct upstream version
Reproduce locally:
cd /path/to/kernel
git checkout qcom-6.18.y
git fetch origin pull/775/head:pr-775
git checkout pr-775
# Run the compliance checker
bash kernel-checkers/check-patch-compliance.sh --kernel-src . \
  --base c9744addfb04eec214121e1fc11040e828576da4 \
  --head e0352b4b7f6706861fb52d4bde2f2217fea5bb5d
Verdict

1 blocker must be fixed before merge:

The check-patch-compliance failure is a critical blocker. The patch content must either:

Match the upstream lore.kernel.org patch exactly, OR

Have the Link: tag removed/updated with an explanation of why the local version differs

All other checkers passed or were correctly skipped (dt-binding-check, dtb-check skipped due to no DT changes; tag-check N/A for stable branch).

qswat-orbit-external · 2026-06-25T13:55:50Z

Merge Check Failed: No Change Task Found

No associated change tasks found for CR 4586059 on any of the following entities:

Entities:

kernel.qli.2.0

CR: 4586059

Please ensure the CR has a change task associated with at least one of the entities for this branch.

qcomlnxci · 2026-06-25T14:39:11Z

Test jobs on e0352b4

qcomlnxci · 2026-06-25T14:39:13Z

Test Matrix

Test Case	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	x1e80100-crd
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
DSP_AudioPD	✅ Pass	✅ Pass	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	◻️
Ethernet	⚠️ skip	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	◻️
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
IPA	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Interrupts	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
OpenCV	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
PCIe	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Probe_Failure_Check	❌ Fail	❌ Fail	✅ Pass	❌ Fail	❌ Fail	❌ Fail	◻️
RMNET	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
USBHost	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
WiFi_Firmware_Driver	❌ Fail	❌ Fail	❌ Fail	✅ Pass	✅ Pass	✅ Pass	◻️
WiFi_OnOff	✅ Pass	❌ Fail	⚠️ skip	✅ Pass	✅ Pass	✅ Pass	◻️
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
gpdsp_remoteproc	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	✅ Pass	❌ Fail	◻️
hotplug	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
irq	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
kaslr	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
pinctrl	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
qcom_hwrng	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
rngtest	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
shmbridge	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
smmu	❌ Fail	✅ Pass	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️
watchdog	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
wpss_remoteproc	✅ Pass	✅ Pass	⚠️ skip	✅ Pass	✅ Pass	✅ Pass	◻️

shashim-quic

remove below lines from commit log. add CRs-Fixed in PR description.

CRs-Fixed: 4583905
qli-2.0 GA Critical Fix

reserved memory Use BUFFER_BYTES_MAX when reserved memory is not configured instead of always using reserved_buf_size, ensuring correct buffer mapping for non-reserved memory platforms. Link: https://lore.kernel.org/all/20260624123748.502781-1-ajay.nandam@oss.qualcomm.com/ Signed-off-by: Ajay Kumar Nandam <ajay.nandam@oss.qualcomm.com>

nandamajay · 2026-06-25T17:38:12Z

remove below lines from commit log. add CRs-Fixed in PR description.

CRs-Fixed: 4583905 qli-2.0 GA Critical Fix

ACK. Removed

qlijarvis · 2026-06-25T18:32:29Z

PR #775 — validate-patch

PR: #775

Verdict	Issues	Detailed Report
⚠️	0	Full report

Final Summary

Lore link present: Yes - properly formatted Link: tag with lore.kernel.org URL
Lore link matches PR commits: Cannot verify - network access restricted, unable to fetch upstream patch for comparison
Upstream patch status: In review - FROMLIST: prefix indicates patch posted to mailing list but not yet merged into mainline
PR present in qcom-next: Not checked - cannot verify without network access to repository

Recommendation: Add a Fixes: tag identifying the commit that introduced the unconditional use of pdata->reserved_buf_size. Once network access is available, verify the diff exactly matches the upstream submission.

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #775 - ASoC: qcom: q6apm-dai: fallback to BUFFER_BYTES_MAX without reserved memory
Upstream commit: https://lore.kernel.org/all/20260624123748.502781-1-ajay.nandam@oss.qualcomm.com/ (cannot verify - network restricted)
Verdict: ⚠️ PARTIAL (cannot verify upstream diff match due to network restrictions)

Commit Message

Check Status Note

Subject matches upstream ⚠️ Cannot verify - network restricted; subject follows kernel style

Body preserves rationale ✅ Clear explanation of the fix and its purpose

Fixes tag present/correct ❌ Missing Fixes: tag - should reference the commit that introduced the bug

Authorship preserved ✅ Author: Ajay Kumar Nandam ajay.nandam@oss.qualcomm.com

Backport note (if applicable) N/A FROMLIST: prefix indicates patch is from mailing list, not yet merged

Diff

File Status Notes

sound/soc/qcom/qdsp6/q6apm-dai.c ⚠️ Cannot verify against upstream - network restricted; diff is syntactically correct

Issues

Missing Fixes: tag - The commit message lacks a Fixes: tag. For a bug fix that addresses incorrect buffer mapping behavior, a Fixes: tag should reference the commit that introduced the problematic code using pdata->reserved_buf_size unconditionally.

Cannot verify upstream match - Network access is restricted, preventing verification that the PR diff exactly matches the lore.kernel.org patch. The lore link is present and properly formatted.

Commit message could be more detailed - While the one-line description is clear, the commit body could benefit from:

More context about when/how the bug manifests

Impact description (what breaks without this fix)

Why BUFFER_BYTES_MAX is the correct fallback value

FROMLIST: prefix - The FROMLIST: prefix indicates this patch is posted to the mailing list but not yet accepted upstream. This is appropriate for patches under review.

Verdict

Cannot fully validate due to network restrictions. The patch structure is correct and follows kernel conventions, but is missing a Fixes: tag. Recommend adding the Fixes: tag before merging. The diff appears reasonable but cannot be verified against upstream source.

Final Summary

Lore link present: Yes - properly formatted Link: tag with lore.kernel.org URL

Lore link matches PR commits: Cannot verify - network access restricted, unable to fetch upstream patch for comparison

Upstream patch status: In review - FROMLIST: prefix indicates patch posted to mailing list but not yet merged into mainline

PR present in qcom-next: Not checked - cannot verify without network access to repository

Recommendation: Add a Fixes: tag identifying the commit that introduced the unconditional use of pdata->reserved_buf_size. Once network access is available, verify the diff exactly matches the upstream submission.

qlijarvis · 2026-06-25T18:32:31Z

PR #775 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	✅	No style issues detected
dt-binding-check	⏭️	Skipped - no DT binding changes
dtb-check	⏭️	Skipped - no devicetree changes
sparse-check	✅	Static analysis passed
check-uapi-headers	✅	No UAPI header changes
check-patch-compliance	❌	BLOCKER: Patch differs from upstream lore link
tag-check	N/A	Not applicable for qcom-6.18.y
qcom-next-check	⏭️	Skipped - FROMLIST prefix present

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #775 - FROMLIST: ASoC: qcom: q6apm-dai: fallback to BUFFER_BYTES_MAX without reserved memory
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/28188903498

Checker Result Summary

checkpatch ✅ No style issues detected

dt-binding-check ⏭️ Skipped - no DT binding changes

dtb-check ⏭️ Skipped - no devicetree changes

sparse-check ✅ Static analysis passed

check-uapi-headers ✅ No UAPI header changes

check-patch-compliance ❌ BLOCKER: Patch differs from upstream lore link

tag-check N/A Not applicable for qcom-6.18.y

qcom-next-check ⏭️ Skipped - FROMLIST prefix present

❌ check-patch-compliance

Root cause: The patch content in the PR differs from the upstream patch referenced in the Link: trailer.

Failure details:
2026-06-25T17:53:04.6629196Z Checking commit: FROMLIST: ASoC: qcom: q6apm-dai: fallback to BUFFER_BYTES_MAX without reserved memory
2026-06-25T17:53:10.3248974Z Change is different from the one mentioned in Link
2026-06-25T17:53:10.3310732Z 
2026-06-25T17:53:10.3328026Z ##[error]Process completed with exit code 1.
The checker compared the PR commit (e5a865cc69c1) against the upstream patch at:
https://lore.kernel.org/all/20260624123748.502781-1-ajay.nandam@oss.qualcomm.com/

and found they are not identical.

Fix:

The check-patch-compliance checker enforces that FROMLIST/UPSTREAM patches must match their upstream source exactly. You have three options:
If the patch was modified intentionally (e.g., context conflict resolution, backport adjustments):

Change the subject prefix from FROMLIST: to BACKPORT: FROMLIST:

Update the commit message to document what was changed and why
If the patch should match upstream exactly:
Fetch the original patch from lore and reapply it cleanly:
b4 am https://lore.kernel.org/all/20260624123748.502781-1-ajay.nandam@oss.qualcomm.com/
git am ./v1_*.mbx
Ensure the diff is byte-for-byte identical to upstream
If the lore link is incorrect:

Update the Link: trailer to point to the correct upstream patch
Reproduce locally:
cd /path/to/kernel
git fetch origin qcom-6.18.y
git checkout qcom-6.18.y
git fetch origin pull/775/head:pr-775
git merge pr-775 --no-commit
bash /path/to/kernel-checkers/check-patch-compliance.sh \
  --kernel-src . \
  --base c9744addfb04eec214121e1fc11040e828576da4 \
  --head e5a865cc69c1c5d9ebc94592e4f10ea2bef49885
Verdict

1 blocker must be fixed before merge: The patch content must either match the upstream lore link exactly (for FROMLIST:), or the subject prefix must be changed to BACKPORT: FROMLIST: with an explanation of the modifications.

qcomlnxci · 2026-06-25T18:59:35Z

Test jobs on e5a865c

qcomlnxci · 2026-06-25T18:59:36Z

Test Matrix

Test Case	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	x1e80100-crd
BT_FW_KMD_Service	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_ON_OFF	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_SCAN	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPUFreq_Validation	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPU_affinity	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
DSP_AudioPD	◻️	✅ Pass	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	◻️
Ethernet	◻️	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	◻️
Freq_Scaling	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
GIC	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
IPA	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Interrupts	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
OpenCV	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
PCIe	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Probe_Failure_Check	◻️	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
RMNET	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
UFS_Validation	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
USBHost	◻️	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
WiFi_Firmware_Driver	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
WiFi_OnOff	◻️	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
adsp_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
cdsp_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
gpdsp_remoteproc	◻️	✅ Pass	⚠️ skip	⚠️ skip	✅ Pass	❌ Fail	◻️
hotplug	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
irq	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
kaslr	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
pinctrl	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
qcom_hwrng	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
rngtest	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
shmbridge	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
smmu	◻️	✅ Pass	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️
watchdog	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
wpss_remoteproc	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️

qcomlnxci · 2026-06-25T19:51:05Z

Test jobs on e5a865c

qcomlnxci · 2026-06-25T19:51:07Z

Test Matrix

Test Case	lemans-evk	monaco-evk	qcs615-ride	qcs6490-rb3gen2	qcs8300-ride	qcs9100-ride-r3	x1e80100-crd
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
DSP_AudioPD	✅ Pass	✅ Pass	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	◻️
Ethernet	⚠️ skip	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip	◻️
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
IPA	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Interrupts	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
OpenCV	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
PCIe	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
RMNET	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
USBHost	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️
WiFi_Firmware_Driver	❌ Fail	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
WiFi_OnOff	✅ Pass	❌ Fail	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
gpdsp_remoteproc	✅ Pass	✅ Pass	⚠️ skip	⚠️ skip	✅ Pass	❌ Fail	◻️
hotplug	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
irq	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
kaslr	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
pinctrl	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
qcom_hwrng	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	❌ Fail	◻️
rngtest	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
shmbridge	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
smmu	❌ Fail	✅ Pass	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️
watchdog	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️

nandamajay requested review from a team, Komal-Bajaj, aiquny and shashim-quic June 25, 2026 12:30

Komal-Bajaj approved these changes Jun 25, 2026

View reviewed changes

shashim-quic requested changes Jun 25, 2026

View reviewed changes

nandamajay force-pushed the shikra_fix branch from e0352b4 to e5a865c Compare June 25, 2026 17:35

qcomlnxci requested review from a team, ndechesne and quic-tingweiz June 25, 2026 17:37

shashim-quic approved these changes Jun 25, 2026

View reviewed changes

qualcomm-linux deleted a comment from qcomlnxci Jun 25, 2026

sgaud-quic merged commit 8c49474 into qualcomm-linux:qcom-6.18.y Jun 25, 2026
6 of 8 checks passed

Uh oh!

Conversation

nandamajay commented Jun 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

qlijarvis commented Jun 25, 2026

PR #775 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Issues

Verdict

Final Summary

Uh oh!

qlijarvis commented Jun 25, 2026

PR #775 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ check-patch-compliance

Verdict

Uh oh!

qswat-orbit-external Bot commented Jun 25, 2026

Uh oh!

qcomlnxci commented Jun 25, 2026

Test jobs on e0352b4

Uh oh!

qcomlnxci commented Jun 25, 2026

Test Matrix

Uh oh!

shashim-quic left a comment

Choose a reason for hiding this comment

Uh oh!

nandamajay commented Jun 25, 2026

Uh oh!

qlijarvis commented Jun 25, 2026

PR #775 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Issues

Verdict

Final Summary

Uh oh!

qlijarvis commented Jun 25, 2026

PR #775 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ check-patch-compliance

Verdict

Uh oh!

qcomlnxci commented Jun 25, 2026

Test jobs on e5a865c

Uh oh!

qcomlnxci commented Jun 25, 2026

Test Matrix

Uh oh!

Uh oh!

qcomlnxci commented Jun 25, 2026

Test jobs on e5a865c

Uh oh!

qcomlnxci commented Jun 25, 2026

Test Matrix

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

nandamajay commented Jun 25, 2026 •

edited

Loading