Skip to content

Revert "LT9611C Device Driver" - #823

Merged
Salendarsingh Gaud (sgaud-quic) merged 14 commits into
qualcomm-linux:qcom-6.18.yfrom
sgaud-quic:display_revert
Jul 14, 2026
Merged

Revert "LT9611C Device Driver" #823
Salendarsingh Gaud (sgaud-quic) merged 14 commits into
qualcomm-linux:qcom-6.18.yfrom
sgaud-quic:display_revert

Conversation

@sgaud-quic

@sgaud-quicSalendarsingh Gaud (sgaud-quic) commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Reverting below PR's :
#762
#765

@qswat-orbit-external

qswat-orbit-externalBot commented Jul 13, 2026

Copy link
Copy Markdown

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

@qswat-orbit-external

qswat-orbit-externalBot commented Jul 13, 2026

Copy link
Copy Markdown

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

@qlijarvis

qlijarvis commented Jul 13, 2026

Copy link
Copy Markdown

PR #823 — validate-patch

PR:#823

VerdictIssuesDetailed Report
⚠️8Full report

Final Summary

  1. Lore link present: No — revert commits don't have lore links; original commits being reverted do have upstream links
  2. Lore link matches PR commits: N/A — these are revert commits, not backports; diff correctly reverses the original changes
  3. Upstream patch status:⚠️ Cannot verify — network restricted; claimed NAKed but unconfirmed; original patches have lore links at https://lore.kernel.org/lkml/20260508134009.4582-3-syyang@lontium.com/ and https://patch.msgid.link/20260107-limit-infoframes-2-v4-5-213d0d3bd490@oss.qualcomm.com
  4. PR present in qcom-next: No — these revert commits are not yet in qcom-next; the original commits being reverted (c78dc5a and b626b1a) are present in qcom-next
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR:#823 - Revert LT9611C Device Driver and drm_bridge changes
Upstream commit: N/A (Revert commits)
Verdict:⚠️ PARTIAL

Analysis Summary

This PR contains two revert commits that undo previously merged changes. The commits being reverted are:

Commit 1:Revert "LT9611C Device Driver (#762)"

Commit 2:Revert "drm: backport drm_bridge changes (#765)"

Commit Message

CheckStatusNote
Subject matches upstreamN/ARevert commits - no upstream equivalent
Body preserves rationale✅States reason for revert (NAK upstream)
Fixes tag present/correctN/ANot applicable for reverts
Authorship preserved✅Authored by submitter (appropriate for reverts)
Backport note (if applicable)N/ANot a backport

Diff

FileStatusNotes
drivers/gpu/drm/bridge/lontium-lt9611c.c✅File deletion (revert)
Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml✅Reverts binding changes
arch/arm64/configs/defconfig✅Removes CONFIG_DRM_LONTIUM_LT9611C
drivers/gpu/drm/bridge/Kconfig✅Removes LT9611C Kconfig entry
drivers/gpu/drm/bridge/Makefile✅Removes build rule
drivers/gpu/drm/bridge/adv7511/adv7511_drv.c✅Reverts InfoFrame callback refactoring
drivers/gpu/drm/bridge/ite-it6263.c✅Reverts InfoFrame callback refactoring
drivers/gpu/drm/bridge/lontium-lt9611.c✅Reverts InfoFrame callback refactoring
drivers/gpu/drm/bridge/synopsys/dw-hdmi-qp.c✅Reverts InfoFrame callback refactoring
drivers/gpu/drm/display/drm_bridge_connector.c✅Reverts connector changes
drivers/gpu/drm/drm_bridge.c✅Reverts bridge core changes
drivers/gpu/drm/msm/hdmi/hdmi_bridge.c✅Reverts InfoFrame callback refactoring
drivers/gpu/drm/rockchip/rk3066_hdmi.c✅Reverts InfoFrame callback refactoring
include/drm/drm_bridge.h✅Reverts header API changes

Issues

⚠️ Upstream Status Verification Blocked:

⚠️ Missing Lore Links in Revert Commits:

  • Neither revert commit includes a Link: tag pointing to the upstream NAK discussion
  • Best practice: revert commits should reference the upstream thread where the NAK occurred

✅ Commit Structure:

  • Both commits properly identify what is being reverted (commit SHA and range)
  • Rationale is provided (NAK upstream)
  • Signed-off-by present

Verdict

Conditional approval pending upstream verification. The revert commits are technically correct in structure and appear to cleanly undo the specified changes. However, the claimed upstream NAK status cannot be verified due to network restrictions. Before merging:

  1. Verify the NAK claim: Confirm that the original patches were actually rejected upstream by checking the lore threads
  2. Add Link tags: Include Link: tags in the commit messages pointing to the upstream NAK discussions for traceability
  3. Consider timing: If the original patches are still under review (not definitively NAKed), consider waiting for final upstream decision

Final Summary

  1. Lore link present: No — revert commits don't have lore links; original commits being reverted do have upstream links
  2. Lore link matches PR commits: N/A — these are revert commits, not backports; diff correctly reverses the original changes
  3. Upstream patch status:⚠️ Cannot verify — network restricted; claimed NAKed but unconfirmed; original patches have lore links at https://lore.kernel.org/lkml/20260508134009.4582-3-syyang@lontium.com/ and https://patch.msgid.link/20260107-limit-infoframes-2-v4-5-213d0d3bd490@oss.qualcomm.com
  4. PR present in qcom-next: No — these revert commits are not yet in qcom-next; the original commits being reverted (c78dc5a and b626b1a) are present in qcom-next

@qlijarvis

qlijarvis commented Jul 13, 2026

Copy link
Copy Markdown

PR #823 — checker-log-analyzer

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

CheckerResultSummary
CheckerResultSummary
checkpatch❌1 warning: DT binding split
dt-binding-check✅Passed
dtb-check⏭️Skipped (no DTS changes)
sparse-check✅Passed
check-uapi-headers✅Passed
check-patch-compliance❌2 commits missing required prefix
tag-check❌2 commits missing required prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR:#823 - Revert LT9611C Device Driver and drm_bridge changes
Source:https://github.com/qualcomm-linux/kernel-config/actions/runs/29239829657

CheckerResultSummary
checkpatch❌1 warning: DT binding split
dt-binding-check✅Passed
dtb-check⏭️Skipped (no DTS changes)
sparse-check✅Passed
check-uapi-headers✅Passed
check-patch-compliance❌2 commits missing required prefix
tag-check❌2 commits missing required prefix

❌ checkpatch

Root cause: Commit f22ed4d modifies both DT binding YAML and driver code in a single patch, violating the kernel's DT binding submission policy.

Failure details:

Commit f22ed4d21b04 ("Revert "LT9611C Device Driver (#762)"")
WARNING: DT binding docs and includes should be a separate patch. See: Documentation/devicetree/bindings/submitting-patches.rst
f22ed4d21b04b6f5d6596091333505ec72420514 total: 0 errors, 1 warnings, 0 checks, 88 lines checked

Fix:

For a revert commit, this warning is a false positive and can be safely ignored. The kernel's DT binding split policy applies to new patches, not to revert commits. A revert must atomically undo all changes from the original commit (including both binding and driver changes) to maintain git history integrity.

No action required — this is an acceptable checkpatch warning for revert commits.

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git e8d06c707464..cd5641992a38

❌ check-patch-compliance

Root cause: Both commits are revert commits without the required upstream-linkable prefix (FROMLIST:, FROMGIT:, UPSTREAM:, or BACKPORT:).

Failure details:

Checking commit: Revert "LT9611C Device Driver (#762)"
Commit summary does not start with a required prefix
Checking commit: Revert "drm: backport drm_bridge changes (#765)"
Commit summary does not start with a required prefix

Fix:

Add an appropriate prefix before the word Revert in each commit subject:

Commit 1:f22ed4d21b04

git rebase -i e8d06c707464 # mark commit as 'edit'
git commit --amend -m "UPSTREAM: Revert \"LT9611C Device Driver (#762)\""# Keep the original commit body unchanged
git rebase --continue

Commit 2:cd5641992a38

# Continue the rebase, mark this commit as 'edit'
git commit --amend -m "UPSTREAM: Revert \"drm: backport drm_bridge changes (#765)\""# Keep the original commit body unchanged
git rebase --continue

Prefix selection rationale:

  • Use UPSTREAM: if the revert itself is being applied to match an upstream revert
  • Use FROMLIST: if the revert is being posted to the mailing list
  • Use QCLINUX: if this is a vendor-only revert (but note: check-patch-compliance will still fail for QCLINUX: — this is a known checker limitation)

For these reverts of previously merged vendor changes, UPSTREAM: is appropriate if the original patches were NAKed upstream and you're aligning with upstream's decision.

❌ tag-check

Root cause: Target branch is qcom-6.18.y (not qcom-next or qcom-next-staging), so every commit must start with a required prefix. Both revert commits are missing the prefix.

Failure details:

Commit f22ed4d21b04 ("Revert "LT9611C Device Driver (#762)""): subject line does not start with a required prefix.

Commit cd5641992a38 ("Revert "drm: backport drm_bridge changes (#765)""): subject line does not start with a required prefix.

All branches except qcom-next and qcom-next-staging require one of:
FROMLIST: / FROMGIT: / UPSTREAM: / BACKPORT: / QCLINUX: / PENDING: / WORKAROUND:

Fix:

Same fix as check-patch-compliance above — add the appropriate prefix before Revert in both commit subjects.

Verdict

2 blockers to fix before merge:

  1. ❌ check-patch-compliance — Add required prefix (UPSTREAM:, FROMLIST:, etc.) before Revert in both commit subjects
  2. ❌ tag-check — Same fix (both checks enforce the same requirement)

The checkpatch warning about DT binding split is a false positive for revert commits and can be ignored.

Recommended action:

git rebase -i e8d06c707464
# Mark both commits as 'edit'# For each commit:
git commit --amend -m "UPSTREAM: Revert \"<original subject>\""
git rebase --continue

After fixing the commit subjects, force-push the branch and re-trigger CI.

@qcomlnxci

qcomlnxci commented Jul 13, 2026

Copy link
Copy Markdown

Test jobs on cd56419

@qcomlnxci

qcomlnxci commented Jul 13, 2026

Copy link
Copy Markdown

Test Matrix

Test Casehamoa-iot-evklemans-evkmonaco-evkqcs615-rideqcs6490-rb3gen2qcs8300-rideqcs9100-ride-r3
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✅ Pass✅ Pass✅ Pass◻️✅ Pass
Ethernet◻️⚠️ skip⚠️ skip⚠️ skip⚠️ skip◻️⚠️ skip
Freq_Scaling◻️✅ Pass✅ Pass✅ Pass❌ Fail◻️✅ Pass
GIC◻️✅ Pass✅ Pass✅ Pass❌ Fail◻️✅ 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❌ Fail❌ Fail❌ Fail◻️✅ Pass
WiFi_OnOff◻️✅ Pass❌ Fail✅ Pass✅ Pass◻️✅ Pass
adsp_remoteproc◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
cdsp_remoteproc◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
gpdsp_remoteproc◻️✅ Pass✅ Pass⚠️ skip⚠️ skip◻️✅ Pass
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◻️✅ Pass
rngtest◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
shmbridge◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
smmu◻️❌ Fail✅ Pass❌ Fail✅ Pass◻️❌ Fail
watchdog◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
wpss_remoteproc◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass

@sgaud-quicSalendarsingh Gaud (sgaud-quic) changed the title Display revertRevert "LT9611C Device Driver" Jul 13, 2026
@qcomlnxci

qcomlnxci commented Jul 13, 2026

Copy link
Copy Markdown

Test jobs on cd56419

@qcomlnxci

qcomlnxci commented Jul 13, 2026

Copy link
Copy Markdown

Test Matrix

Test Casehamoa-iot-evklemans-evkmonaco-evkqcs615-rideqcs6490-rb3gen2qcs8300-rideqcs9100-ride-r3
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✅ Pass✅ Pass✅ Pass◻️✅ Pass
Ethernet◻️⚠️ skip⚠️ skip⚠️ skip⚠️ skip◻️⚠️ skip
Freq_Scaling◻️✅ Pass✅ Pass✅ Pass❌ Fail◻️✅ Pass
GIC◻️✅ Pass✅ Pass✅ Pass❌ Fail◻️✅ 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❌ Fail❌ Fail❌ Fail◻️✅ Pass
WiFi_OnOff◻️✅ Pass❌ Fail✅ Pass✅ Pass◻️✅ Pass
adsp_remoteproc◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
cdsp_remoteproc◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
gpdsp_remoteproc◻️✅ Pass✅ Pass⚠️ skip⚠️ skip◻️✅ Pass
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◻️✅ Pass
rngtest◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
shmbridge◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
smmu◻️❌ Fail✅ Pass❌ Fail✅ Pass◻️❌ Fail
watchdog◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
wpss_remoteproc◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass

@qswat-orbit-external

qswat-orbit-externalBot commented Jul 13, 2026

Copy link
Copy Markdown

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

@qcomlnxci
qcomlnxci requested a review from a teamJuly 13, 2026 15:50
@qlijarvis

qlijarvis commented Jul 13, 2026

Copy link
Copy Markdown

PR #823 — validate-patch

PR:#823

VerdictIssuesDetailed Report
❌5Full report

Final Summary

  1. Lore link present: No — none of the 14 revert commits include lore.kernel.org links to the original patches being reverted
  2. Lore link matches PR commits: N/A — no lore links to compare against
  3. Upstream patch status: Cannot verify — commit messages claim "NAKed in upstream" but provide no thread reference or maintainer quote as evidence
  4. PR present in qcom-next: Not checked — validation cannot proceed without lore links
Verdict: ❌ — click to expand

🔍 Patch Validation

PR:#823 - Revert LT9611C bridge driver patches (14 commits)
Upstream commit: None found
Verdict: ❌ FAIL

Commit Message

CheckStatusNote
Subject matches upstream❌No lore links provided for original commits being reverted
Body preserves rationale⚠️States "Commit is NAKed in upstream" but no evidence provided
Fixes tag present/correctN/ANot applicable to revert commits
Authorship preserved✅Revert author is the submitter
Backport note (if applicable)N/ANot applicable to revert commits

Diff

FileStatusNotes
All 14 commits❌Cannot validate without lore links to original patches

Issues

Critical: No lore links provided for validation

This PR contains 14 revert commits that revert FROMLIST and BACKPORT patches:

  • Commits 1-12: Revert FROMLIST patches
  • Commits 13-14: Revert BACKPORT patches

According to the validate-patch skill, revert commits should be validated against the original lore posting being reverted. However, none of the 14 commit messages include lore.kernel.org links to the original patches.

Each commit message states "Commit is NAKed in upstream, so reverting for now" but provides:

  • ❌ No lore.kernel.org link to the original patch thread
  • ❌ No evidence of the NAK (no maintainer quote, no thread reference)
  • ❌ No way to verify the revert diff is the correct inverse of the original patch

Example from commit 01/14:

Subject: [PATCH 01/14] Revert "FROMLIST: arm64: defconfig: Enable LT9611C bridge driver"
Commit is NAKed in upstream,
so reverting for now.
This reverts commit 2f074adbd0574c7565653cf5ab061a7c58ff99ee.

What's missing:

Link: https://lore.kernel.org/r/<message-id-of-original-patch>

Without the lore links, this skill cannot:

  1. Verify that the patches were actually NAKed (no thread evidence)
  2. Validate that the revert diffs correctly undo the original patches
  3. Check whether the original patches have since been accepted in a revised form
  4. Confirm the revert is necessary and appropriate

Verdict

❌ FAIL — Cannot validate without lore links

All 14 commits must be amended to include Link: tags pointing to the lore.kernel.org threads for the original FROMLIST/BACKPORT patches being reverted.

Recommendation

Before merging, add lore links to all 14 commits:

For each revert commit, add a Link: line referencing the original lore thread:

Subject: [PATCH XX/14] Revert "FROMLIST: <original subject>"
Commit is NAKed in upstream,
so reverting for now.
This reverts commit <sha>.
Link: https://lore.kernel.org/r/<message-id-of-original-patch>
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>

How to find the lore links:

  1. Check out the commit being reverted: git show <sha>
  2. Extract the Link: tag from the original commit message
  3. Add that link to the revert commit message

Additional recommendation:

Include evidence of the NAK in the commit message. For example:

Commit is NAKed in upstream by <maintainer> on <date>:
"<quote from NAK message>"
Link: https://lore.kernel.org/r/<message-id>

This provides reviewers with:

  • Verifiable evidence of the rejection
  • Context for why the revert is necessary
  • Traceability to the upstream discussion

Final Summary

  1. Lore link present: No — none of the 14 revert commits include lore.kernel.org links to the original patches being reverted
  2. Lore link matches PR commits: N/A — no lore links to compare against
  3. Upstream patch status: Cannot verify — commit messages claim "NAKed in upstream" but provide no thread reference or maintainer quote as evidence
  4. PR present in qcom-next: Not checked — validation cannot proceed without lore links

@qlijarvis

qlijarvis commented Jul 13, 2026

Copy link
Copy Markdown

PR #823 — checker-log-analyzer

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

CheckerResultSummary
CheckerResultSummary
checkpatch❌1 commit with 3 undocumented DT string warnings
dt-binding-check✅Passed
dtb-check⏭️Skipped (no DTS changes)
sparse-check✅Passed
check-uapi-headers✅Passed
check-patch-compliance❌All 14 commits missing required prefix before "Revert"
tag-check❌All 14 commits missing required prefix (if not targeting qcom-next/qcom-next-staging)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR:#823 - Revert LT9611C bridge driver patches
Source:https://github.com/qualcomm-linux/kernel-config/actions/runs/29263910872

CheckerResultSummary
checkpatch❌1 commit with 3 undocumented DT string warnings
dt-binding-check✅Passed
dtb-check⏭️Skipped (no DTS changes)
sparse-check✅Passed
check-uapi-headers✅Passed
check-patch-compliance❌All 14 commits missing required prefix before "Revert"
tag-check❌All 14 commits missing required prefix (if not targeting qcom-next/qcom-next-staging)

❌ checkpatch

Root cause: Revert commit re-introduces code with undocumented DT compatible strings.

Failure details:

Commit 16456b388d71 ("Revert "FROMLIST: drm-bridge: lontium lt9611c: fixes and improvements"")
WARNING: DT compatible string "lontium,lt9611c" appears un-documented
#95: FILE: drivers/gpu/drm/bridge/lontium-lt9611c.c:1217:
+	{ .compatible = "lontium,lt9611c" },
WARNING: DT compatible string "lontium,lt9611ex" appears un-documented
#96: FILE: drivers/gpu/drm/bridge/lontium-lt9611c.c:1218:
+	{ .compatible = "lontium,lt9611ex" },
WARNING: DT compatible string "lontium,lt9611uxd" appears un-documented
#97: FILE: drivers/gpu/drm/bridge/lontium-lt9611c.c:1219:
+	{ .compatible = "lontium,lt9611uxd" },
16456b388d71 total: 0 errors, 3 warnings, 0 checks, 73 lines checked

Fix: These warnings are expected for a revert commit that restores old code. The compatible strings were likely documented in the patches being reverted. Since this is a revert of NAKed upstream patches, the warnings can be accepted as-is. However, if the binding file Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml exists and documents these strings, the warnings are false positives.

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git <base>..16456b388d71

❌ check-patch-compliance

Root cause: All 14 Revert commits lack a required prefix before the word "Revert".

Failure details:

Checking commit: Revert "FROMLIST: arm64: defconfig: Enable LT9611C bridge driver"
Commit summary does not start with a required prefix
Checking commit: Revert "FROMLIST: drm/bridge: lt9611c: clean up probe error and remove paths"
Commit summary does not start with a required prefix
[... repeated for all 14 commits ...]

Fix: Add a valid prefix before "Revert" in each commit subject. The checker accepts: FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:.

For revert commits, the prefix should reflect where the revert itself comes from or will be posted:

  • If reverting because upstream NAKed the patches → use UPSTREAM: Revert or FROMLIST: Revert
  • If this is a vendor-only revert → use QCLINUX: Revert (but note: QCLINUX: will still fail this checker due to known limitation)

Example fix:

git rebase -i <base_sha># For each commit, mark as 'edit'
git commit --amend -m "UPSTREAM: Revert \"FROMLIST: arm64: defconfig: Enable LT9611C bridge driver\""
git rebase --continue

Reproduce locally:

# The checker script expects commits to start with FROMLIST:/FROMGIT:/UPSTREAM:/BACKPORT:# Revert commits without a prefix will always fail

❌ tag-check (conditional)

Root cause: All 14 commits are missing the mandatory subject-line prefix tag.

Applies when: The PR target branch is notqcom-next or qcom-next-staging.

Failure details:
All 14 commit subjects start with Revert "..." without a leading prefix tag. According to the tag-check rules, every commit merged into branches other than qcom-next or qcom-next-staging must start with one of:

  • FROMLIST: / FROMGIT: / UPSTREAM: / BACKPORT: / QCLINUX: / PENDING: / WORKAROUND:

Fix: Same as check-patch-compliance fix above. Add the appropriate prefix before "Revert":

git rebase -i <base_sha># For each commit:
git commit --amend -m "UPSTREAM: Revert \"FROMLIST: <original subject>\""# or
git commit --amend -m "FROMLIST: Revert \"FROMLIST: <original subject>\""

Note: If this PR targets qcom-next or qcom-next-staging, this check does not apply and can be marked as N/A.

Reproduce locally:

# Check each commit subject:
git log <base>..<head> --format="%H %s"| grep -v -E '^[a-f0-9]+ (FROMLIST|FROMGIT|UPSTREAM|BACKPORT|QCLINUX|PENDING|WORKAROUND):'

Verdict

2 blockers to fix before merge:

  1. check-patch-compliance failure — All 14 Revert commits need a valid prefix (UPSTREAM:, FROMLIST:, FROMGIT:, or BACKPORT:) before the word "Revert".

  2. tag-check failure (conditional) — If the target branch is notqcom-next or qcom-next-staging, all 14 commits require a subject-line prefix tag. This is the same fix as Create qualcomm-linux-organization-repolinter.yml #1.

Non-blocker:

  • checkpatch warnings — The 3 undocumented DT string warnings in commit 16456b3 are expected for a revert that restores old code. These can be accepted as-is if the binding documentation exists or was removed by the patches being reverted.

Recommended action:

  1. Confirm the target branch for this PR.
  2. If targeting any branch except qcom-next/qcom-next-staging, rebase all 14 commits to add the appropriate prefix (e.g., UPSTREAM: Revert "..." or FROMLIST: Revert "...").
  3. The checkpatch warnings can be accepted without changes.

@qcomlnxci

qcomlnxci commented Jul 13, 2026

Copy link
Copy Markdown

Test jobs on cae8653

@qcomlnxci

qcomlnxci commented Jul 13, 2026

Copy link
Copy Markdown

Test Matrix

Test Casehamoa-iot-evklemans-evkmonaco-evkqcs615-rideqcs6490-rb3gen2
BT_FW_KMD_Service◻️✅ Pass✅ Pass✅ Pass✅ Pass
BT_ON_OFF◻️✅ Pass✅ Pass✅ Pass✅ Pass
BT_SCAN◻️✅ Pass✅ Pass✅ Pass✅ Pass
CPUFreq_Validation◻️✅ Pass✅ Pass✅ Pass✅ Pass
CPU_affinity◻️✅ Pass✅ Pass✅ Pass✅ Pass
DSP_AudioPD◻️✅ Pass✅ Pass✅ Pass✅ Pass
Ethernet◻️⚠️ skip⚠️ skip⚠️ skip⚠️ skip
Freq_Scaling◻️✅ Pass✅ Pass✅ Pass✅ Pass
GIC◻️✅ Pass✅ Pass✅ Pass✅ Pass
IPA◻️✅ Pass✅ Pass✅ Pass✅ Pass
Interrupts◻️✅ Pass✅ Pass✅ Pass✅ Pass
OpenCV◻️✅ Pass✅ Pass✅ Pass✅ Pass
PCIe◻️✅ Pass✅ Pass✅ Pass✅ Pass
Probe_Failure_Check◻️❌ Fail❌ Fail✅ Pass❌ Fail
RMNET◻️✅ Pass✅ Pass✅ Pass✅ Pass
UFS_Validation◻️✅ Pass✅ Pass✅ Pass✅ Pass
USBHost◻️❌ Fail❌ Fail❌ Fail❌ Fail
WiFi_Firmware_Driver◻️✅ Pass❌ Fail✅ Pass✅ Pass
WiFi_OnOff◻️✅ Pass❌ Fail⚠️ skip✅ Pass
adsp_remoteproc◻️✅ Pass✅ Pass✅ Pass✅ Pass
cdsp_remoteproc◻️✅ Pass✅ Pass✅ Pass✅ Pass
gpdsp_remoteproc◻️✅ Pass✅ Pass⚠️ skip⚠️ skip
hotplug◻️✅ Pass✅ Pass✅ Pass✅ Pass
irq◻️✅ Pass✅ Pass✅ Pass✅ Pass
kaslr◻️✅ Pass✅ Pass✅ Pass✅ Pass
pinctrl◻️✅ Pass✅ Pass✅ Pass✅ Pass
qcom_hwrng◻️✅ Pass✅ Pass✅ Pass✅ Pass
remoteproc◻️✅ Pass✅ Pass✅ Pass✅ Pass
rngtest◻️✅ Pass✅ Pass✅ Pass✅ Pass
shmbridge◻️✅ Pass✅ Pass✅ Pass✅ Pass
smmu◻️❌ Fail✅ Pass❌ Fail✅ Pass
watchdog◻️✅ Pass✅ Pass✅ Pass✅ Pass
wpss_remoteproc◻️✅ Pass✅ Pass✅ Pass✅ Pass

@sgaud-quic
Revert "FROMLIST: arm64: defconfig: Enable LT9611C bridge driver"
f6882fa
Commit is NAKed in upstream, so reverting for now.
This reverts commit 2f074ad.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic
Revert "FROMLIST: drm/bridge: lt9611c: clean up probe error and remov…
7f5c8de
…e paths"
Commit is NAKed in upstream, so reverting for now.
This reverts commit 1a9b2e0.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic
Revert "FROMLIST: drm/bridge: lt9611c: fix chip type initialization"
b2a91ca
Commit is NAKed in upstream, so reverting for now.
This reverts commit ec012bf.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic
Revert "FROMLIST: drm/bridge: lt9611c: fix DT parsing and bridge refc…
77ba6a0
…ount"
Commit is NAKed in upstream, so reverting for now.
This reverts commit e4d89a3.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic
Revert "FROMLIST: drm/bridge: lt9611c: implement hpd_enable callback"
5c905cb
Commit is NAKed in upstream, so reverting for now.
This reverts commit f28f9a0.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic
Revert "FROMLIST: drm/bridge: lt9611c: fallback to cached HPD status …
29c4241
…on read failure"
Commit is NAKed in upstream, so reverting for now.
This reverts commit 87dab5e.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic
Revert "FROMLIST: drm/bridge: lontium-lt9611c: Add DSI port selection…
a106c5b
… via DT property"
Commit is NAKed in upstream, so reverting for now.
This reverts commit 7108379.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic
Revert "FROMLIST: drm-bridge: lontium lt9611c: fixes and improvements"
94d580a
Commit is NAKed in upstream, so reverting for now.
This reverts commit 4c28ed9.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic
Revert "FROMLIST: drm/bridge: lontium-lt9611c: Increase MCU poll time…
5a41d54
…out to 200ms"
Commit is NAKed in upstream, so reverting for now.
This reverts commit 316abfa.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic
Revert "FROMLIST: dt-bindings: brige: lt9611c: add port-select proper…
3641d9d
…ty for LT9611C"
Commit is NAKed in upstream, so reverting for now.
This reverts commit 7aa4c19.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic
Revert "FROMLIST: drm/bridge: Add Lontium LT9611C(EX/UXD) MIPI DSI to…
9e528e0
… HDMI driver"
Commit is NAKed in upstream, so reverting for now.
This reverts commit 3b7c779.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic
Revert "FROMLIST: dt-bindings: bridge: Add Lontium LT9611C(EX/UXD) MI…
4145118
…PI DSI to HDMI driver"
Commit is NAKed in upstream, so reverting for now.
This reverts commit 27f88bf.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic
Revert "BACKPORT: drm/bridge: refactor HDMI InfoFrame callbacks"
6b8493e
Reverting as the dependency change is NAKed.
This reverts commit 994dee7.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@sgaud-quic
Revert "BACKPORT: drm/bridge: add next_bridge pointer to struct drm_b…
4f2d1ef
…ridge"
Reverting as the dependency change is NAKed.
This reverts commit 22affbc.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>
@qswat-orbit-external

qswat-orbit-externalBot commented Jul 14, 2026

Copy link
Copy Markdown

Merge Check Failed: No CR Numbers Found

Error: No Change Request numbers were found.

Please add Change Request numbers to your pull request description in the format CRs-Fixed: 12345 or link GitHub issues that are associated with Change Requests.

@qlijarvis

qlijarvis commented Jul 14, 2026

Copy link
Copy Markdown

PR #823 — validate-patch

PR:#823

VerdictIssuesDetailed Report
❌8Full report

Final Summary

  1. Lore link present: No — none of the 14 revert commits include lore.kernel.org links to the original patches being reverted
  2. Lore link matches PR commits: N/A — no lore links to compare against
  3. Upstream patch status: Unknown — claims of "NAKed in upstream" cannot be verified without lore links or evidence
  4. PR present in qcom-next: Not checked — revert commits; would need to verify the original commits being reverted are present in qcom-next
Verdict: ❌ — click to expand

🔍 Patch Validation

PR:#823 - Revert NAKed LT9611C bridge driver patches
Upstream commit: N/A (no lore links provided)
Verdict: ❌ FAIL

Commit Message

CheckStatusNote
Subject matches upstreamN/ARevert commits without lore links
Body preserves rationale⚠️States "NAKed in upstream" but provides no evidence
Fixes tag present/correctN/ANot applicable for reverts
Authorship preserved✅Consistent author (sgaud@qti.qualcomm.com)
Backport note (if applicable)N/ANot applicable

Diff

FileStatusNotes
All files⚠️Cannot verify revert correctness without lore links to original patches

Issues

Critical: Missing lore links for all 14 revert commits

According to the validate-patch skill workflow, revert commits should link to the original lore posting being reverted. None of the 14 commits in this PR include such links.

Commits 1-12 (FROMLIST reverts):

  • Subject pattern: Revert "FROMLIST: <original subject>"
  • Commit message: "Commit is NAKed in upstream, so reverting for now."
  • Missing: Link to the lore.kernel.org thread showing the NAK
  • Missing: Evidence of the NAK (maintainer name, date, quote)

Commits 13-14 (BACKPORT reverts):

  • Subject pattern: Revert "BACKPORT: <original subject>"
  • Commit message: "Reverting as the dependency change is NAKed."
  • Missing: Link to the lore.kernel.org thread showing the NAK
  • Missing: Explanation of which dependency was NAKed

Recommended fixes:

  1. Add lore links to each revert commit message showing the original patch posting
  2. Add evidence of the NAK with format: NAK from <maintainer> on <date>: "<quote>"
  3. For commits 13-14, clarify which dependency was NAKed and link to that thread

Example improved commit message:

Revert "FROMLIST: drm/bridge: lt9611c: clean up probe error and remove paths"
This patch was NAKed by <maintainer> on the mailing list.
NAK from <maintainer> on YYYY-MM-DD:
"<quote from NAK message>"
Link: https://lore.kernel.org/r/<message-id>
This reverts commit 1a9b2e035afd6845cfa6f953c71a83d60ecad5c2.
Signed-off-by: Salendarsingh Gaud <sgaud@qti.qualcomm.com>

Verdict

Do not merge without adding lore links and NAK evidence.

While the technical content of the reverts appears correct (they cleanly revert the specified commits), the commit messages lack the required upstream references and evidence. For revert commits, especially those claiming upstream NAK, it is essential to:

  1. Link to the original lore posting
  2. Provide verifiable evidence of the NAK
  3. Allow reviewers to independently verify the upstream decision

Without these links, reviewers cannot verify:

  • Whether the patches were actually NAKed
  • The reason for the NAK
  • Whether the entire patch series should be reverted or only specific commits
  • Whether there are alternative approaches being discussed upstream

Final Summary

  1. Lore link present: No — none of the 14 revert commits include lore.kernel.org links to the original patches being reverted
  2. Lore link matches PR commits: N/A — no lore links to compare against
  3. Upstream patch status: Unknown — claims of "NAKed in upstream" cannot be verified without lore links or evidence
  4. PR present in qcom-next: Not checked — revert commits; would need to verify the original commits being reverted are present in qcom-next

@qlijarvis

qlijarvis commented Jul 14, 2026

Copy link
Copy Markdown

PR #823 — checker-log-analyzer

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

CheckerResultSummary
CheckerResultSummary
checkpatch❌1 commit with 3 UNDOCUMENTED_DT_STRING warnings
dt-binding-check✅Passed
dtb-check⏭️Skipped (no DTS changes)
sparse-check✅Passed
check-uapi-headers✅Passed
check-patch-compliance❌14 commits missing required prefix
tag-check❌14 commits missing required prefix (mandatory for qcom-6.18.y)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR:#823 - Revert LT9611C bridge driver patches
Source:https://github.com/qualcomm-linux/kernel-config/actions/runs/29304173097
Target Branch:qcom-6.18.y

CheckerResultSummary
checkpatch❌1 commit with 3 UNDOCUMENTED_DT_STRING warnings
dt-binding-check✅Passed
dtb-check⏭️Skipped (no DTS changes)
sparse-check✅Passed
check-uapi-headers✅Passed
check-patch-compliance❌14 commits missing required prefix
tag-check❌14 commits missing required prefix (mandatory for qcom-6.18.y)

❌ checkpatch

Root cause: Commit 94d580a42961 ("Revert "FROMLIST: drm-bridge: lontium lt9611c: fixes and improvements"") re-introduces undocumented DT compatible strings.

Failure details:

WARNING: DT compatible string "lontium,lt9611c" appears un-documented -- check ./Documentation/devicetree/bindings/
#94: FILE: drivers/gpu/drm/bridge/lontium-lt9611c.c:1217:
+	{ .compatible = "lontium,lt9611c" },
WARNING: DT compatible string "lontium,lt9611ex" appears un-documented -- check ./Documentation/devicetree/bindings/
#95: FILE: drivers/gpu/drm/bridge/lontium-lt9611c.c:1218:
+	{ .compatible = "lontium,lt9611ex" },
WARNING: DT compatible string "lontium,lt9611uxd" appears un-documented -- check ./Documentation/devicetree/bindings/
#96: FILE: drivers/gpu/drm/bridge/lontium-lt9611c.c:1219:
+	{ .compatible = "lontium,lt9611uxd" },
94d580a42961b13f960ca7dd313bf4aadce8e8cd total: 0 errors, 3 warnings, 0 checks, 73 lines checked

Analysis: This is a revert commit that brings back the old lontium-lt9611c.c driver. The warnings are expected because the revert removes the binding documentation that was added in the original patches. These are not blockers for a revert operation — the warnings indicate the reverted state lacks documentation, which is the intended outcome of reverting the feature.

Fix: No action required. These warnings are expected for a revert that removes a feature and its documentation.

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git e8d06c707464437c26e5ad72fe052c57253b552a..4f2d1efb2eb54d8973ccc0f355a293082debab00

❌ check-patch-compliance

Root cause: All 14 commits are Revert commits that lack a required prefix before the word "Revert".

Failure details:

Checking commit: Revert "FROMLIST: arm64: defconfig: Enable LT9611C bridge driver"
Commit summary does not start with a required prefix
Checking commit: Revert "FROMLIST: drm/bridge: lt9611c: clean up probe error and remove paths"
Commit summary does not start with a required prefix
[... 12 more commits with identical failure ...]
Checking commit: Revert "BACKPORT: drm/bridge: add next_bridge pointer to struct drm_bridge"
Commit summary does not start with a required prefix

Analysis: The check-patch-compliance checker enforces that commit subjects start with one of: FROMLIST:, FROMGIT:, UPSTREAM:, or BACKPORT:. Revert commits must have a prefix before the word Revert.

All 14 commits in this PR are revert commits with subjects like:

  • Revert "FROMLIST: ..."
  • Revert "BACKPORT: ..."

The correct format should be:

  • UPSTREAM: Revert "FROMLIST: ..."
  • FROMLIST: Revert "FROMLIST: ..."
  • BACKPORT: Revert "BACKPORT: ..."

Fix:

git rebase -i e8d06c707464437c26e5ad72fe052c57253b552a
# For each commit, mark as 'edit', then:
git commit --amend -m "UPSTREAM: Revert \"FROMLIST: <original subject>\""# or
git commit --amend -m "FROMLIST: Revert \"FROMLIST: <original subject>\""
git rebase --continue

Choose the appropriate prefix based on the revert's origin:

  • If the revert itself is posted upstream → FROMLIST:
  • If the revert is merged upstream → UPSTREAM:
  • If the revert is a backport → BACKPORT:

Reproduce locally:

# The checker runs automatically in CI# To test locally, clone kernel-checkers and run:
bash kernel-checkers/check-patch-compliance.sh --kernel-src . \
--base e8d06c707464437c26e5ad72fe052c57253b552a \
--head 4f2d1efb2eb54d8973ccc0f355a293082debab00

❌ tag-check

Root cause: Target branch is qcom-6.18.y (not qcom-next or qcom-next-staging), which requires every commit subject to start with a valid prefix tag. All 14 commits are missing this required prefix.

Failure details:

The PR targets qcom-6.18.y, which mandates that every commit subject must start with one of:

  • FROMLIST: / FROMGIT: / UPSTREAM: / BACKPORT: / QCLINUX: / PENDING: / WORKAROUND:

All 14 commits have subjects starting with Revert without a leading prefix:

❌ Commit f6882fa104d9: "Revert "FROMLIST: arm64: defconfig: Enable LT9611C bridge driver""
❌ Commit 7f5c8de28e1f: "Revert "FROMLIST: drm/bridge: lt9611c: clean up probe error and remove paths""
❌ Commit b2a91ca1f09b: "Revert "FROMLIST: drm/bridge: lt9611c: fix chip type initialization""
❌ Commit 77ba6a010a65: "Revert "FROMLIST: drm/bridge: lt9611c: fix DT parsing and bridge refcount""
❌ Commit 5c905cbdf604: "Revert "FROMLIST: drm/bridge: lt9611c: implement hpd_enable callback""
❌ Commit 29c42412542a: "Revert "FROMLIST: drm/bridge: lt9611c: fallback to cached HPD status on read failure""
❌ Commit a106c5bcbb0a: "Revert "FROMLIST: drm/bridge: lontium-lt9611c: Add DSI port selection via DT property""
❌ Commit 94d580a42961: "Revert "FROMLIST: drm-bridge: lontium lt9611c: fixes and improvements""
❌ Commit 5a41d54e7c08: "Revert "FROMLIST: drm/bridge: lontium-lt9611c: Increase MCU poll timeout to 200ms""
❌ Commit 3641d9dddb56: "Revert "FROMLIST: dt-bindings: brige: lt9611c: add port-select property for LT9611C""
❌ Commit 9e528e0994e3: "Revert "FROMLIST: drm/bridge: Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI driver""
❌ Commit 4145118e73a6: "Revert "FROMLIST: dt-bindings: bridge: Add Lontium LT9611C(EX/UXD) MIPI DSI to HDMI driver""
❌ Commit 6b8493e9cea2: "Revert "BACKPORT: drm/bridge: refactor HDMI InfoFrame callbacks""
❌ Commit 4f2d1efb2eb5: "Revert "BACKPORT: drm/bridge: add next_bridge pointer to struct drm_bridge""

Analysis: This is the same root cause as check-patch-compliance, but tag-check is a mandatory requirement for all branches except qcom-next and qcom-next-staging. Since the target is qcom-6.18.y, every commit must carry a prefix.

Fix: Same as check-patch-compliance — add a prefix before Revert:

git rebase -i e8d06c707464437c26e5ad72fe052c57253b552a
# For each commit (all 14), mark as 'edit', then amend:
git commit --amend -m "UPSTREAM: Revert \"FROMLIST: <original subject>\""# or
git commit --amend -m "FROMLIST: Revert \"FROMLIST: <original subject>\""
git rebase --continue

Reproduce locally:

# List all commits and check for missing prefixes:
git log e8d06c707464437c26e5ad72fe052c57253b552a..4f2d1efb2eb54d8973ccc0f355a293082debab00 --format="%H %s"| \
whileread sha subject;doif!echo"$subject"| grep -qE '^(FROMLIST|FROMGIT|UPSTREAM|BACKPORT|QCLINUX|PENDING|WORKAROUND):';thenecho"MISSING prefix: $sha$subject"fidone

Verdict

14 blockers must be fixed before merge.

All 14 commits require subject line amendments to add a valid prefix before Revert. The checkpatch warnings are expected for revert commits and do not block merge.

Required action: Rebase the PR and prepend each commit subject with an appropriate prefix (UPSTREAM:, FROMLIST:, or BACKPORT:) before the word Revert.

@qcomlnxci

qcomlnxci commented Jul 14, 2026

Copy link
Copy Markdown

Test jobs on 4f2d1ef

@qcomlnxci

qcomlnxci commented Jul 14, 2026

Copy link
Copy Markdown

Test Matrix

Test Casehamoa-iot-evklemans-evkmonaco-evkqcs615-rideqcs6490-rb3gen2qcs8300-rideqcs9100-ride-r3
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✅ Pass✅ Pass✅ Pass◻️✅ Pass
Ethernet◻️⚠️ skip⚠️ 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◻️✅ Pass❌ Fail✅ Pass✅ Pass◻️✅ Pass
WiFi_OnOff◻️✅ Pass❌ Fail✅ Pass✅ Pass◻️✅ Pass
adsp_remoteproc◻️✅ Pass◻️✅ Pass✅ Pass◻️✅ Pass
cdsp_remoteproc◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
gpdsp_remoteproc◻️✅ Pass✅ Pass⚠️ skip⚠️ skip◻️✅ Pass
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◻️✅ Pass
rngtest◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
shmbridge◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
smmu◻️❌ Fail✅ Pass❌ Fail✅ Pass◻️❌ Fail
watchdog◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass
wpss_remoteproc◻️✅ Pass✅ Pass✅ Pass✅ Pass◻️✅ Pass

@sgaud-quic
Salendarsingh Gaud (sgaud-quic) merged commit 48143db into qualcomm-linux:qcom-6.18.yJul 14, 2026
5 of 8 checks passed
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@shashim-quicShiraz Hashim (shashim-quic)shashim-quic approved these changes
@trsoniTrilok Soni (trsoni)Awaiting requested review from trsonitrsoni was automatically assigned from qualcomm-linux/qualcomm-kernel-maint
@quic-tingweizTingwei Zhang (quic-tingweiz)Awaiting requested review from quic-tingweizquic-tingweiz was automatically assigned from qualcomm-linux/qualcomm-kernel-maint
@knaveen-qcknaveen-qcAwaiting requested review from knaveen-qcknaveen-qc was automatically assigned from qualcomm-linux/qualcomm-kernel-maint

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@sgaud-quic@qlijarvis@qcomlnxci@shashim-quic