FROMLIST: media: iris: Fix VSP clock calculation for high bitrate str… by venvenk · Pull Request #1250 · qualcomm-linux/kernel

venvenk · 2026-10-07T12:11:14Z

…eams

Frame drops were observed during high-resolution streams decoded at high bitrates, as well as concurrent decode sessions. Analysis showed that the Video Signal Processor (VSP) clock requirement was underestimated for these workloads, resulting in insufficient clock scaling and reduced processing throughput.

Update the VSP frequency calculation to more accurately reflect the processing requirements of different codecs and bitrates, ensuring that the requested clock frequency is sufficient to sustain the workload and prevent frame drops.

Link: https://lore.kernel.org/all/20261006-fix-vsp-freq-calc-v1-1-53532d893852@oss.qualcomm.com
CRs-fixed: 4653264

qswat-orbit-external · 2026-10-07T12:11:21Z

Merge Check Failed: No Change Task Found

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

Entities:

kernel.qli.2.0

CR: 4653264

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

…eams Frame drops were observed during high-resolution streams decoded at high bitrates, as well as concurrent decode sessions. Analysis showed that the Video Signal Processor (VSP) clock requirement was underestimated for these workloads, resulting in insufficient clock scaling and reduced processing throughput. Update the VSP frequency calculation to more accurately reflect the processing requirements of different codecs and bitrates, ensuring that the requested clock frequency is sufficient to sustain the workload and prevent frame drops. Link: https://lore.kernel.org/all/20261006-fix-vsp-freq-calc-v1-1-53532d893852@oss.qualcomm.com Signed-off-by: Vishnu Reddy <busanna.reddy@oss.qualcomm.com> Signed-off-by: Venkata Siva Pavan KumarVenkatapatigari <venvenk@qti.qualcomm.com> Signed-off-by: Nagesh Jamakhandi <njamakha@qti.qualcomm.com>

qcomlnxci · 2026-10-09T11:23:57Z

Test Matrix

Test Case	hamoa-iot-evk-multimedia	lemans-evk-multimedia	monaco-evk-multimedia	purwa-iot-evk-multimedia	qcs615-ride-multimedia	qcs6490-rb3gen2-multimedia	qcs8300-ride-multimedia	qcs9100-ride-r3-multimedia	shikra-iqs-evk-multimedia
Audio_Card_Registration	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	⚠️ skip	⚠️ skip	⚠️ skip
BT_FW_KMD_Service	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_ON_OFF	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
BT_SCAN	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	❌ Fail
CPUFreq_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
CPU_affinity	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
DSP_AudioPD	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
Ethernet_Basic_Validation	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	◻️	⚠️ skip	⚠️ skip	⚠️ skip	⚠️ skip
Freq_Scaling	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
GIC	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	❌ Fail
IPA	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
Interrupts	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
KVM_Driver	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	❌ Fail
KVM_EL2_DTB	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	❌ Fail
KVM_Infra	❌ Fail	✅ Pass	✅ Pass	❌ Fail	◻️	✅ Pass	❌ Fail	❌ Fail	❌ Fail
OpenCV	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
PCIe	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	❌ Fail
Probe_Failure_Check	❌ Fail	❌ Fail	❌ Fail	❌ Fail	◻️	❌ Fail	❌ Fail	❌ Fail	❌ Fail
RMNET	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
UFS_Validation	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
USBHost	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	⚠️ skip	✅ Pass	✅ Pass	❌ Fail
WiFi_Firmware_Driver	✅ Pass	✅ Pass	❌ Fail	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
WiFi_OnOff	✅ Pass	✅ Pass	❌ Fail	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
adsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	⚠️ skip
cdsp_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
gpdsp_remoteproc	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip	◻️	⚠️ skip	✅ Pass	✅ Pass	⚠️ skip
hotplug	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
irq	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
kaslr	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
pinctrl	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
qcom_hwrng	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	◻️
rngtest	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
shmbridge	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
smmu	❌ Fail	❌ Fail	✅ Pass	❌ Fail	◻️	✅ Pass	✅ Pass	❌ Fail	✅ Pass
watchdog	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass
wpss_remoteproc	✅ Pass	✅ Pass	✅ Pass	✅ Pass	◻️	✅ Pass	✅ Pass	✅ Pass	✅ Pass

qcomlnxci · 2026-10-09T11:25:26Z

Test jobs on a309154

qlijarvis · 2026-10-10T00:22:19Z

PR #1250 — validate-patch

PR: #1250

Verdict	Issues	Detailed Report
⚠️	0	Full report

Final Summary

Lore link present: Yes — https://lore.kernel.org/all/20261006-fix-vsp-freq-calc-v1-1-53532d893852@oss.qualcomm.com
Lore link matches PR commits: Yes — diff content is identical; line number shifts are due to legitimate tree context differences
Upstream patch status: ⏳ Decision Pending — posted Oct 6, 2026; no maintainer replies yet (no ACK/NAK/applied signals in thread)
PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1250 - FROMLIST: media: iris: Fix VSP clock calculation for high bitrate streams
Upstream commit: https://lore.kernel.org/all/20261006-fix-vsp-freq-calc-v1-1-53532d893852@oss.qualcomm.com
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note

Subject matches upstream ✅ FROMLIST: prefix added correctly; base subject identical

Body preserves rationale ✅ Problem description and fix rationale preserved verbatim

Fixes tag present/correct ⚠️ Missing — lore has Fixes: 82b96a8d8d6e ("media: iris: Move vpu35 specific api to common to use for vpu4") and Cc: stable@vger.kernel.org; PR omits both

Authorship preserved ✅ From: matches lore author (Vishnu Reddy); original Signed-off-by: present

Backport note (if applicable) N/A Not a backport — FROMLIST: prefix indicates pending upstream patch

Diff

File Status Notes

drivers/media/platform/qcom/iris/iris_vpu_common.c:423 ✅ Code changes identical; context line numbers differ (423 vs 454) due to tree delta — legitimate adaptation

Issues

Missing Fixes: tag — The upstream lore patch includes Fixes: 82b96a8d8d6e ("media: iris: Move vpu35 specific api to common to use for vpu4") and Cc: stable@vger.kernel.org, but the PR commit message omits both. These tags are critical for stable backport tracking and should be preserved.

Verdict

The code diff is faithful to the lore patch. The commit message body is correct, but the missing Fixes: tag and Cc: stable@ line should be added before merging to maintain proper stable backport metadata.

Final Summary

Lore link present: Yes — https://lore.kernel.org/all/20261006-fix-vsp-freq-calc-v1-1-53532d893852@oss.qualcomm.com

Lore link matches PR commits: Yes — diff content is identical; line number shifts are due to legitimate tree context differences

Upstream patch status: ⏳ Decision Pending — posted Oct 6, 2026; no maintainer replies yet (no ACK/NAK/applied signals in thread)

PR present in qcom-next/topics: Yes — integration_presence_report.md confirms all added lines are present in topics (1/1 commits present)

Deterministic Integration Presence

Integration Presence Report

This report is generated by Jarvis before validate-patch runs.
It is the authoritative source for whether PR changes are already present
in qcom-next or in the kernel topic branches.

Kernel repo: /local/mnt/workspace/sgaud/Qgenie/image_pipeline/kernel
qcom-next ref: ba86f67908354f41f269ca1d64b22e4624766dcf
topics remote: topics -> https://github.com/qualcomm-linux/kernel-topics
topics fetch: fetched

Commit Subject qcom-next topics Final

1/1 [PATCH] FROMLIST: media: iris: Fix VSP clock calculation for high missing - no subject, patch-id, or full tree-content match found present - all checked added lines are present present

Final Status

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

qlijarvis · 2026-10-10T00:22:20Z

PR #1250 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	1 warning: Unknown commit id in Fixes tag
dt-binding-check	⏭️	No DT binding changes
dtb-check	⏭️	No DTS changes
sparse-check	✅	Passed (pre-existing warnings only)
check-uapi-headers	✅	Passed
check-patch-compliance	❌	Author mismatch
tag-check	✅	Subject has valid `FROMLIST:` prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1250 - FROMLIST: media: iris: Fix VSP clock calculation for high bitrate streams
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/37619589367

Checker Result Summary

checkpatch ❌ 1 warning: Unknown commit id in Fixes tag

dt-binding-check ⏭️ No DT binding changes

dtb-check ⏭️ No DTS changes

sparse-check ✅ Passed (pre-existing warnings only)

check-uapi-headers ✅ Passed

check-patch-compliance ❌ Author mismatch

tag-check ✅ Subject has valid FROMLIST: prefix

❌ checkpatch

Root cause: The Fixes: tag references commit 82b96a8d8d6e which is not reachable in the current tree (likely from a topic branch or not yet merged).

Failure details:
WARNING: Unknown commit id '82b96a8d8d6e', maybe rebased or not pulled?
#19: 
Fixes: 82b96a8d8d6e ("media: iris: Move vpu35 specific api to common to use for vpu4")

c12ad4a57d29e9f24e91ed4a89a753ace4221410 total: 0 errors, 1 warnings, 0 checks, 46 lines checked
Fix:

This warning occurs when the commit referenced in the Fixes: tag is not present in the base branch. You have three options:
If the referenced commit is in a topic branch: This is acceptable for integration branches. The warning can be ignored as the commit will be present when the topic branch is merged.
If the commit SHA is incorrect: Verify the correct SHA from the upstream tree:
git log --oneline --grep="media: iris: Move vpu35 specific api to common to use for vpu4"
Then update the Fixes: tag with the correct SHA.
If the Fixes tag is not needed: Remove the Fixes: tag entirely:
git rebase -i <base_sha>   # mark commit as 'edit'
# Edit commit message to remove Fixes: line
git commit --amend
git rebase --continue
Reproduce locally:
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 9d6b44a8ec46..c12ad4a57d29
❌ check-patch-compliance

Root cause: The commit author in git metadata (Venkata Siva Pavan KumarVenkatapatigari <venvenk@qti.qualcomm.com>) does not match the original author from the lore.kernel.org patch (Vishnu Reddy <busanna.reddy@oss.qualcomm.com>).

Failure details:
Checking commit: FROMLIST: media: iris: Fix VSP clock calculation for high bitrate streams
Author mismatch:
  Original author: Vishnu Reddy <busanna.reddy@oss.qualcomm.com>
  Commit author : Venkata Siva Pavan KumarVenkatapatigari <venvenk@qti.qualcomm.com>
Fix:

The git commit author must match the original patch author from the mailing list. Update the commit author:
git rebase -i <base_sha>   # mark commit as 'edit'
git commit --amend --author="Vishnu Reddy <busanna.reddy@oss.qualcomm.com>"
git rebase --continue
Note: The current commit has:

Author (From:): Venkata Siva Pavan KumarVenkatapatigari <venvenk@qti.qualcomm.com> ❌

Signed-off-by: Vishnu Reddy <busanna.reddy@oss.qualcomm.com> (original author)

Signed-off-by: Venkata Siva Pavan KumarVenkatapatigari <venvenk@qti.qualcomm.com> (committer)

Signed-off-by: Nagesh Jamakhandi <njamakha@qti.qualcomm.com> (reviewer)

The git Author: field should be Vishnu Reddy <busanna.reddy@oss.qualcomm.com> to match the upstream patch. The other Signed-off-by: lines correctly document the chain of custody.

Reproduce locally:
b4 am --single-message -C -l -3 https://lore.kernel.org/all/20261006-fix-vsp-freq-calc-v1-1-53532d893852@oss.qualcomm.com -o /tmp/out
# Compare author field
git show c12ad4a57d29 --format="%an <%ae>" --no-patch
cat /tmp/out/*.mbx | grep "^From:"
Verdict

2 blockers must be fixed before merge:

Author mismatch (BLOCKER): Update git commit author to match the original upstream author Vishnu Reddy <busanna.reddy@oss.qualcomm.com>.

Unknown commit in Fixes tag (ADVISORY): The Fixes: tag references commit 82b96a8d8d6e which is not in the base branch. If this commit is in a topic branch that will be merged, the warning can be ignored. Otherwise, verify the correct SHA or remove the Fixes: tag.

All other checkers passed or were correctly skipped (no DT/DTS changes).

qlijarvis · 2026-10-10T03:04:50Z

PR #1250 — validate-patch

PR: #1250

Verdict	Issues	Detailed Report
⚠️	0	Full report

Final Summary

Lore link present: Yes — https://lore.kernel.org/all/20261006-fix-vsp-freq-calc-v1-1-53532d893852@oss.qualcomm.com
Lore link matches PR commits: Yes — diff content is identical; commit message body matches but missing Fixes: and Cc: stable tags
Upstream patch status: ⏳ In review — posted Oct 6, 2026; no maintainer response yet (4 days old)
PR present in qcom-next/topics: Yes - all 1 commit(s) are present in qcom-next or topics

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1250 — FROMLIST: media: iris: Fix VSP clock calculation for high bitrate streams
Upstream commit: https://lore.kernel.org/all/20261006-fix-vsp-freq-calc-v1-1-53532d893852@oss.qualcomm.com
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note

Subject matches upstream ✅ FROMLIST: prefix correctly added

Body preserves rationale ✅ Both paragraphs identical to lore

Fixes tag present/correct ❌ Missing — lore has Fixes: 82b96a8d8d6e

Authorship preserved ✅ Original author's Signed-off-by: present (FROMLIST rule satisfied)

Backport note (if applicable) N/A Not a backport — FROMLIST commit

Cc: stable tag ❌ Missing — lore has Cc: stable@vger.kernel.org

Link tag ✅ Correct lore URL added

Diff

File Status Notes

drivers/media/platform/qcom/iris/iris_vpu_common.c ✅ Code changes identical to lore patch

Issues

Missing Fixes: tag — The lore patch includes Fixes: 82b96a8d8d6e ("media: iris: Move vpu35 specific api to common to use for vpu4") which should be preserved in the PR commit message.

Missing Cc: stable@vger.kernel.org — The lore patch targets stable backport; this tag should be included in the PR commit message.

Additional Signed-off-by: lines — The PR adds two internal reviewers' sign-offs not present in the lore patch. This is acceptable for internal review chain-of-custody but means the PR commit differs from what will eventually land upstream.

Verdict

The code diff is faithful to the lore patch, but the commit message is missing critical metadata (Fixes: tag and Cc: stable tag). These should be added before merging to maintain proper attribution and stable backport tracking.

Recommendation: Request the submitter to add the missing Fixes: and Cc: stable@vger.kernel.org tags to the commit message, then approve.

Final Summary

Lore link present: Yes — https://lore.kernel.org/all/20261006-fix-vsp-freq-calc-v1-1-53532d893852@oss.qualcomm.com

Lore link matches PR commits: Yes — diff content is identical; commit message body matches but missing Fixes: and Cc: stable tags

Upstream patch status: ⏳ In review — posted Oct 6, 2026; no maintainer response yet (4 days old)

PR present in qcom-next/topics: Yes — all added lines are present in kernel topic branches (per integration_presence_report.md)

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

Commit Subject qcom-next topics Final

1/1 [PATCH] FROMLIST: media: iris: Fix VSP clock calculation for high missing - no subject, patch-id, or full tree-content match found present - all checked added lines are present present

Final Status

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

qlijarvis · 2026-10-10T03:04:51Z

PR #1250 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	1 warning: missing `Fixes:` tag
dt-binding-check	⏭️	No DT binding changes
dtb-check	⏭️	No DTS changes
sparse-check	✅	Passed
check-uapi-headers	✅	Passed
check-patch-compliance	✅	Passed
tag-check	✅	Subject has valid `FROMLIST:` prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1250 - FROMLIST: media: iris: Fix VSP clock calculation for high bitrate streams
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/37729607551

Checker Result Summary

checkpatch ❌ 1 warning: missing Fixes: tag

dt-binding-check ⏭️ No DT binding changes

dtb-check ⏭️ No DTS changes

sparse-check ✅ Passed

check-uapi-headers ✅ Passed

check-patch-compliance ✅ Passed

tag-check ✅ Subject has valid FROMLIST: prefix

❌ checkpatch

Root cause: Commit message mentions stable@ in the body but lacks a corresponding Fixes: tag.

Failure details:
WARNING: The commit message has 'stable@', perhaps it also needs a 'Fixes:' tag?

376ebb539862a0cf4a9578d4f00dca4ed6034131 total: 0 errors, 1 warnings, 0 checks, 46 lines checked

Commit 376ebb539862 ("FROMLIST: media: iris: Fix VSP clock calculation for high bitrate streams") has style problems, please review.
Analysis:
This is a WARNING (not an ERROR), meaning it's a style suggestion rather than a hard blocker. The checker detected that the commit message body likely references stable@ (typically in a Cc: stable@vger.kernel.org line), which usually indicates a bug fix that should also include a Fixes: tag pointing to the commit that introduced the issue.

However, reviewing the patch content in pr.patch, I don't see an explicit Cc: stable@ line in the commit message. This may be a false positive triggered by pattern matching in the commit body text.

Fix (if Cc: stable@ is present):
If the commit body contains Cc: stable@vger.kernel.org, add a Fixes: tag before it:
git rebase -i 4c5c1a4c37fc   # mark commit as 'edit'
# Edit commit message to add:
# Fixes: <sha> ("<original commit subject>")
git commit --amend
git rebase --continue
Fix (if this is a false positive):
If there's no Cc: stable@ line and this is a false positive, the warning can be safely ignored. The patch is otherwise clean.

Reproduce locally:
./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git 4c5c1a4c37fc..376ebb539862
Verdict

1 non-blocking warning. The checkpatch warning is a style suggestion (WARNING, not ERROR). If the commit genuinely references stable@ and fixes a regression, add a Fixes: tag. Otherwise, this can be merged as-is — all other checkers passed cleanly.

Salendarsingh Gaud (sgaud-quic) · 2026-10-10T03:47:26Z

venvenk please add Fixes: tag to the commit :

❌ checkpatch
Root cause: Commit message mentions stable@ in the body but lacks a corresponding Fixes: tag.

venvenk requested review from a team, Dmitry Baryshkov (lumag), Trilok Soni (trsoni) and yijiyang October 7, 2026 12:11

venvenk force-pushed the qcom-6.18.y branch from c12ad4a to 376ebb5 Compare October 8, 2026 04:50

venvenk force-pushed the qcom-6.18.y branch from 376ebb5 to a309154 Compare October 9, 2026 05:34

vgarodia approved these changes Oct 9, 2026

View reviewed changes

Shiraz Hashim (shashim-quic) approved these changes Oct 9, 2026

View reviewed changes

Conversation

venvenk commented Oct 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

qswat-orbit-external Bot commented Oct 7, 2026

Uh oh!

qcomlnxci commented Oct 9, 2026

Test Matrix

Uh oh!

qcomlnxci commented Oct 9, 2026

Test jobs on a309154

Uh oh!

qlijarvis commented Oct 10, 2026

PR #1250 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Issues

Verdict

Final Summary

Deterministic Integration Presence

Integration Presence Report

Final Status

Uh oh!

qlijarvis commented Oct 10, 2026

PR #1250 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ checkpatch

❌ check-patch-compliance

Verdict

Uh oh!

qlijarvis commented Oct 10, 2026

PR #1250 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Issues

Verdict

Final Summary

Deterministic Integration Presence

Integration Presence Report

Final Status

Uh oh!

qlijarvis commented Oct 10, 2026

PR #1250 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ checkpatch

Verdict

Uh oh!

Salendarsingh Gaud (sgaud-quic) commented Oct 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

venvenk commented Oct 7, 2026 •

edited

Loading