Vote qref in tcsr driver by qianyu-qcom · Pull Request #1473 · qualcomm-linux/kernel-topics

qianyu-qcom · 2026-07-03T14:22:26Z

No description provided.

The QREF block supplies reference clocks to PCIe PHYs and requires dedicated LDO supplies to operate. The digital control interface for QREF (clkref_en registers) resides in TCSR on glymur. Since QREF has no dedicated DT node of its own, these supply properties are placed in the TCSR node which acts as the control interface for QREF. Add a dedicated binding file for qcom,glymur-tcsr and document the supply properties. As this binding will grow to cover more SoCs, mark the required supplies per compatible using an allOf/if/then conditional. Link: https://lore.kernel.org/all/20260702-tcsr_qref_0702-v7-0-776f2811b7af@oss.qualcomm.com/ Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>

Mahua shares the same QREF TX/RPT/RX component naming as Glymur, but has a different topology: a single QREF block fed by REFGEN4 only, rather than the two independent blocks fed by REFGEN3 and REFGEN4 on Glymur. Add qcom,mahua-tcsr compatible and document its required supply properties. Note that REFGEN4 is supplied by regulators vdda-refgen3-1p2 and vdda-refgen3-0p9 on Mahua. List: https://lore.kernel.org/all/20260702-tcsr_qref_0702-v7-0-776f2811b7af@oss.qualcomm.com/ Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>

Before XO refclk is distributed to PCIe/USB/eDP PHYs, it passes through a QREF block. QREF is powered by dedicated LDO rails, and the clkref_en register controls whether refclk is gated through to the PHY side. These clkref controls are different from typical GCC branch clocks: - only a single enable bit is present, without branch-style config bits - regulators must be voted before enable and unvoted after disable Model this as a dedicated clk_ref clock type with custom clk_ops instead of reusing struct clk_branch semantics. Also provide a common registration/probe API so the same clkref model can be reused regardless of where clkref_en registers are placed, e.g. TCSR on glymur and TLMM on SM8750. Link: https://lore.kernel.org/all/20260702-tcsr_qref_0702-v7-0-776f2811b7af@oss.qualcomm.com/ Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>

…e to clk_ref helper Replace local clk_branch-based clkref definitions with descriptor-based registration via qcom_clk_ref_probe(). This keeps the glymur driver focused on clock metadata and reuses common runtime logic for regulator handling, enable/disable sequencing, and OF provider wiring. Link: https://lore.kernel.org/all/20260702-tcsr_qref_0702-v7-0-776f2811b7af@oss.qualcomm.com/ Co-developed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>

Mahua is based on Glymur but uses a different QREF topology, requiring distinct regulator lists and clock descriptors for its PCIe clock references. Add mahua-specific regulator arrays and clk descriptor table, and use match_data to select the correct descriptor table per compatible string at probe time. Link: https://lore.kernel.org/all/20260702-tcsr_qref_0702-v7-0-776f2811b7af@oss.qualcomm.com/ Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>

qlijarvis · 2026-07-03T20:11:20Z

🔨 Build Failure Analysis — PR #1473

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

#	Error	File:Line	PR-introduced?	Root Cause
1	Merge conflict (add/add)	`Documentation/devicetree/bindings/cpufreq/qcom,shikra-epss.yaml`	No	Pre-existing conflict between base branch and topic branch during automerge
2	Merge conflict (content)	`Documentation/devicetree/bindings/crypto/qcom,prng.yaml`	No	Pre-existing conflict between base branch and topic branch during automerge
3	Merge conflict (content)	`Documentation/devicetree/bindings/crypto/qcom-qce.yaml`	No	Pre-existing conflict between base branch and topic branch during automerge
4	Merge conflict (content)	`Documentation/devicetree/bindings/display/msm/gpu.yaml`	No	Pre-existing conflict between base branch and topic branch during automerge
5+	Multiple additional merge conflicts	Various DT binding files	No	Pre-existing conflicts in interconnect, iommu, media, phy, regulator, remoteproc bindings and driver files

Verdict

0 of 11+ errors are introduced by this PR; all are pre-existing merge conflicts in the base branch.

This is NOT a compilation failure. The build failed during the automerge phase when attempting to merge tech/bsp/clk topic branch with the qcom-next baseline. The PR changes (adding qcom,glymur-tcsr.yaml, clk-ref.c, and include/linux/clk/qcom.h) do not conflict with any of the failing files.

📎 Detailed analysis: Full report

qlijarvis · 2026-07-03T20:15:30Z

🔨 Build Failure Analysis — PR #1473

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

#	Error	File:Line	PR-introduced?	Root Cause
N/A	No compilation errors	N/A	N/A	Build failed during integration merge, not compilation

Verdict

This PR introduces zero compilation errors. The build failure is caused by 101 merge conflicts during the automerge/integration workflow when merging the tech/bsp/clk topic branch with other topic branches. None of the conflicting files are modified by this PR.

📎 Detailed analysis: Full report

qlijarvis · 2026-07-03T20:34:52Z

PR #1473 — validate-patch

PR: #1473

Verdict	Issues	Detailed Report
⚠️	6	Full report

Final Summary

Lore link present: Yes — all 5 commits link to https://lore.kernel.org/all/20260702-tcsr_qref_0702-v7-0-776f2811b7af@oss.qualcomm.com/ (commit 2 uses "List:" tag instead of "Link:")
Lore link matches PR commits: Cannot verify — network access restricted, unable to fetch upstream patches for comparison
Upstream patch status: Cannot verify — network access restricted, unable to check mailing list thread for acceptance/rejection/pending status
PR present in qcom-next: Cannot verify — git repository access slow/restricted, search timed out after 25+ seconds

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1473 - FROMLIST: dt-bindings and clk: qcom: Add QREF regulator support for glymur and mahua TCSR
Upstream commit: https://lore.kernel.org/all/20260702-tcsr_qref_0702-v7-0-776f2811b7af@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL (network restrictions prevent full validation)

Commit Message

Check Status Note

Subject matches upstream ⏭️ Cannot verify - network access restricted

Body preserves rationale ✅ All commits have descriptive commit messages

Fixes tag present/correct N/A No Fixes tags (new feature, not a fix)

Authorship preserved ✅ All commits authored by Qiang Yu; FROMLIST allows submitter in From:

Backport note (if applicable) N/A FROMLIST commits, not backports

Lore links present ✅ All 5 commits have lore.kernel.org links

Trailer consistency ⚠️ Commit 2 uses "List:" instead of "Link:"

Diff

File Status Notes

Documentation/devicetree/bindings/clock/qcom,glymur-tcsr.yaml ⏭️ Cannot verify against upstream - network restricted

Documentation/devicetree/bindings/clock/qcom,sm8550-tcsr.yaml ⏭️ Cannot verify against upstream - network restricted

drivers/clk/qcom/clk-ref.c ⏭️ Cannot verify against upstream - network restricted

include/linux/clk/qcom.h ⏭️ Cannot verify against upstream - network restricted

drivers/clk/qcom/tcsrcc-glymur.c ⏭️ Cannot verify against upstream - network restricted

drivers/clk/qcom/Makefile ⏭️ Cannot verify against upstream - network restricted

Issues

Minor Issues:

Commit 2 trailer inconsistency: Uses List: instead of Link: for the lore.kernel.org URL. While both are acceptable, Link: is the standard tag used in commits 1, 3, 4, and 5. Recommend changing to Link: for consistency.

Validation Limitations:
2. Cannot fetch upstream patches: Network access is restricted, preventing download of the lore.kernel.org patch series for diff comparison.
3. Cannot verify upstream status: Unable to check if patches have been accepted, rejected, or are pending on the mailing list.
4. Cannot verify qcom-next presence: Git repository access is slow/restricted, preventing verification of whether commits are already in qcom-next.

Positive Observations:

All 5 commits correctly use the FROMLIST: prefix

All commits have lore.kernel.org links pointing to the same v7 patch series

Author is consistent (Qiang Yu qiang.yu@oss.qualcomm.com) across all commits

Commit 4 has proper Co-developed-by/Signed-off-by/Reviewed-by trailer ordering

Commit messages are descriptive and explain the rationale for changes

No obvious authorship issues (FROMLIST allows submitter to differ from original author)

Verdict

Cannot fully validate due to network restrictions. Based on available information:

✅ Commit message structure: Proper FROMLIST prefix, lore links present, authorship consistent
⚠️ Minor fix needed: Change List: to Link: in commit 2 for consistency
⏭️ Diff faithfulness: Cannot verify without upstream patches
⏭️ Upstream status: Cannot verify without lore.kernel.org access
⏭️ qcom-next presence: Cannot verify due to slow repo access

Recommendation: The PR structure appears correct for FROMLIST commits. The only actionable issue is the trailer tag inconsistency in commit 2. If network access were available, full validation would include:

Fetching the v7 patch series from lore.kernel.org

Comparing each commit's diff against the corresponding upstream patch

Checking the mailing list thread for acceptance/rejection signals

Verifying presence in qcom-next branch

Final Summary

Lore link present: Yes — all 5 commits link to https://lore.kernel.org/all/20260702-tcsr_qref_0702-v7-0-776f2811b7af@oss.qualcomm.com/ (commit 2 uses "List:" tag instead of "Link:")

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

Upstream patch status: Cannot verify — network access restricted, unable to check mailing list thread for acceptance/rejection/pending status

PR present in qcom-next: Cannot verify — git repository access slow/restricted, search timed out after 25+ seconds

qlijarvis · 2026-07-03T20:34:53Z

PR #1473 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	CI infrastructure failure - merge failed
dt-binding-check	❌	CI infrastructure failure - merge failed
dtb-check	❌	CI infrastructure failure - merge failed
sparse-check	❌	CI infrastructure failure - merge failed
check-uapi-headers	❌	CI infrastructure failure - merge failed
check-patch-compliance	❌	CI infrastructure failure - merge failed
tag-check	⏭️	Cannot evaluate - CI did not run checkers

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1473 - FROMLIST: dt-bindings: clock: qcom: Move glymur TCSR to own binding (+ 4 more commits)
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/28680919137

Checker Result Summary

checkpatch ❌ CI infrastructure failure - merge failed

dt-binding-check ❌ CI infrastructure failure - merge failed

dtb-check ❌ CI infrastructure failure - merge failed

sparse-check ❌ CI infrastructure failure - merge failed

check-uapi-headers ❌ CI infrastructure failure - merge failed

check-patch-compliance ❌ CI infrastructure failure - merge failed

tag-check ⏭️ Cannot evaluate - CI did not run checkers

❌ CI Infrastructure Failure (All Checkers)

Root cause: The CI workflow failed during the merge setup phase before any checkers could run. All checker jobs encountered fatal: refusing to merge unrelated histories when attempting to merge the PR branch with the integration baseline.

Failure details:
2026-07-03T20:15:24.4525428Z Fetching PR #1473 from https://github.com/qualcomm-linux/kernel-topics.git...
2026-07-03T20:15:25.1062168Z From https://github.com/qualcomm-linux/kernel-topics
2026-07-03T20:15:25.1062750Z  * [new ref]                   refs/pull/1473/head -> pr-1473
2026-07-03T20:15:25.1265720Z Merging pr-1473 (no-commit)...
2026-07-03T20:15:45.4296639Z fatal: refusing to merge unrelated histories
2026-07-03T20:15:45.5454564Z Merge failed or conflicts detected. Aborting merge.
2026-07-03T20:15:45.5473024Z fatal: There is no merge to abort (MERGE_HEAD missing).
2026-07-03T20:15:45.5491534Z ##[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 PR branch (topic/tech/bsp/clk) and the integration baseline (19b282f417584cfe14ce6a262122c51553d026ec) do not share a common ancestor in their git history. This is a CI configuration or workflow issue, not a problem with the patch content itself.

Possible causes:

Orphan branch: The PR branch may have been created as an orphan branch with no connection to the main repository history

Wrong baseline: The CI may be attempting to merge against an incorrect baseline commit

Repository mismatch: The topic branch and baseline may be from different repository forks with divergent histories

CI workflow bug: The automerge configuration may have incorrect branch references

Fix:

This is a CI infrastructure issue that requires investigation by the repository maintainers. The patches themselves cannot be evaluated until the merge setup is fixed.

Recommended actions:
Verify branch ancestry: Check that topic/tech/bsp/clk is based on a commit that exists in the baseline history:
git merge-base --is-ancestor <baseline-commit> <pr-head-commit>
Check automerge configuration: Review the .github/workflows/ configuration and the automerge conf file to ensure the baseline and topic branch references are correct.
Rebase if needed: If the PR branch is truly orphaned, it may need to be rebased onto the correct baseline:
git rebase --onto <correct-baseline> --root topic/tech/bsp/clk
Re-trigger CI: Once the branch ancestry issue is resolved, re-trigger the CI workflow.
Note on patch content:

From the PR patch file, all 5 commits have proper FROMLIST: prefixes and include Link: tags pointing to lore.kernel.org, which suggests the patches themselves follow proper formatting conventions. However, no actual checker validation could be performed due to the merge failure.

The commits in this PR are:

FROMLIST: dt-bindings: clock: qcom: Move glymur TCSR to own binding

FROMLIST: dt-bindings: clock: qcom,glymur-tcsr: Add mahua support

FROMLIST: clk: qcom: Add generic clkref_en support

FROMLIST: clk: qcom: tcsrcc-glymur: Add regulator supplies and migrate to clk_ref helper

FROMLIST: clk: qcom: tcsrcc-glymur: Add Mahua QREF regulator support

Verdict

Cannot merge - CI infrastructure failure prevents validation. The merge setup must be fixed before the patches can be evaluated by the kernel checkers. This is not a patch quality issue; it is a repository/workflow configuration problem that requires maintainer intervention.

The QREF block supplies reference clocks to PCIe/USB/UFS PHYs and requires dedicated LDO supplies to operate. The digital control interface for QREF (clkref_en registers) resides in TCSR on x1e80100. Since QREF has no dedicated DT node of its own, these supply properties are placed in the TCSR node which acts as the control interface for QREF. Add a dedicated binding file for qcom,x1e80100-tcsr and document the supply properties. Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>

Replace local clk_branch-based clkref definitions with descriptor-based registration via qcom_clk_ref_probe(). This keeps the x1e80100 driver focused on clock metadata and reuses common runtime logic for regulator handling, enable/disable sequencing, and OF provider wiring. Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>

qlijarvis · 2026-07-10T05:36:37Z

PR #1473 — validate-patch

PR: #1473

Verdict	Issues	Detailed Report
⚠️	0	Full report

Final Summary

Lore link present: Partial - Commits 1, 3-5 have Link: tags; commit 2 has typo (List: instead of Link:); commits 6-7 are PENDING (no link expected)
Lore link matches PR commits: Cannot verify - lore patches dated July 2026 are not yet accessible; network access restricted
Upstream patch status: ⏳ In review - Patches posted as v7 series on July 2, 2026; cannot verify acceptance status (lore not accessible)
PR present in qcom-next: No - Commits dated July 2-7, 2026 are newer than qcom-next HEAD (June 28, 2026); expected to land in a future qcom-next update

Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #1473 - TCSR QREF clock controller bindings and driver updates
Upstream commits: Multiple lore.kernel.org links (series v7)
Verdict: ⚠️ PARTIAL

Summary by Commit

Commit 1/7: FROMLIST: dt-bindings: clock: qcom: Move glymur TCSR to own binding

Lore link: https://lore.kernel.org/all/20260702-tcsr_qref_0702-v7-0-776f2811b7af@oss.qualcomm.com/

Status: ⚠️ Link points to cover letter (v7-0), not the specific patch (should be v7-1)

Commit 2/7: FROMLIST: dt-bindings: clock: qcom,glymur-tcsr: Add mahua support

Lore link: Uses "List:" instead of "Link:" (typo)

Status: ❌ FAIL - Incorrect trailer tag

Commit 3/7: FROMLIST: clk: qcom: Add generic clkref_en support

Lore link: https://lore.kernel.org/all/20260702-tcsr_qref_0702-v7-0-776f2811b7af@oss.qualcomm.com/

Status: ⚠️ Link points to cover letter (v7-0), not the specific patch (should be v7-3)

Commit 4/7: FROMLIST: clk: qcom: tcsrcc-glymur: Add regulator

Lore link: https://lore.kernel.org/all/20260702-tcsr_qref_0702-v7-0-776f2811b7af@oss.qualcomm.com/

Status: ⚠️ Link points to cover letter (v7-0), not the specific patch (should be v7-4)

Commit 5/7: FROMLIST: clk: qcom: tcsrcc-glymur: Add Mahua QREF

Lore link: https://lore.kernel.org/all/20260702-tcsr_qref_0702-v7-0-776f2811b7af@oss.qualcomm.com/

Status: ⚠️ Link points to cover letter (v7-0), not the specific patch (should be v7-5)

Commit 6/7: PENDING: dt-bindings: clock: qcom: Move x1e80100 TCSR to own binding

Lore link: None (expected for PENDING prefix)

Status: ✅ PASS - Correct for PENDING commits

Commit 7/7: PENDING: clk: qcom: tcsrcc-x1e80100: Migrate to clk_ref

Lore link: None (expected for PENDING prefix)

Status: ✅ PASS - Correct for PENDING commits

Commit Message

Check Status Note

Subject matches upstream ⏭️ Skipped Cannot verify - lore patches not accessible (future date: July 2026)

Body preserves rationale ⏭️ Skipped Cannot verify - lore patches not accessible

Fixes tag present/correct N/A No Fixes tags in any commit

Authorship preserved ✅ All commits authored by Qiang Yu qiang.yu@oss.qualcomm.com

Backport note (if applicable) N/A FROMLIST commits, not backports

Diff

File Status Notes

All files ⏭️ Skipped Cannot compare - upstream lore patches not accessible (network restricted + future date)

Issues

Commit 2/7 - Incorrect trailer tag: Uses List: instead of Link: for the lore.kernel.org URL. This should be Link: to match kernel conventions and the other commits in this series.

Commits 1, 3, 4, 5 - Cover letter links: All Link: tags point to the series cover letter (v7-0) rather than the specific patch message-ID. While this provides series context, best practice is to link to the individual patch message-ID (e.g., v7-1 for commit 1, v7-3 for commit 3, etc.) so reviewers can directly access the specific patch discussion.

Cannot verify diff content: The lore patches are dated July 2026 (future) and are not yet accessible on lore.kernel.org. Network access is also restricted in this environment. Therefore, diff comparison against upstream cannot be performed.

Verdict

⚠️ PARTIAL - Fix commit 2's trailer tag before merging. Consider updating Link tags to point to individual patch message-IDs rather than the cover letter for better traceability.

Required fix:

Commit 2: Change List: https://lore.kernel.org/... to Link: https://lore.kernel.org/...

Recommended improvements:

Update all Link: tags to point to the specific patch message-ID (v7-1, v7-2, v7-3, v7-4, v7-5) instead of the cover letter (v7-0)

Final Summary

Lore link present: Partial - Commits 1, 3-5 have Link: tags; commit 2 has typo (List: instead of Link:); commits 6-7 are PENDING (no link expected)

Lore link matches PR commits: Cannot verify - lore patches dated July 2026 are not yet accessible; network access restricted

Upstream patch status: ⏳ In review - Patches posted as v7 series on July 2, 2026; cannot verify acceptance status (lore not accessible)

PR present in qcom-next: No - Commits dated July 2-7, 2026 are newer than qcom-next HEAD (June 28, 2026); expected to land in a future qcom-next update

qlijarvis · 2026-07-10T05:36:38Z

PR #1473 — checker-log-analyzer

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

Checker	Result	Summary
Checker	Result	Summary
checkpatch	⏭️	CI infrastructure failure - unable to merge PR
dt-binding-check	⏭️	CI infrastructure failure - unable to merge PR
dtb-check	⏭️	CI infrastructure failure - unable to merge PR
sparse-check	⏭️	CI infrastructure failure - unable to merge PR
check-uapi-headers	⏭️	CI infrastructure failure - unable to merge PR
check-patch-compliance	⏭️	CI infrastructure failure - unable to merge PR
tag-check	✅	All commits have valid prefixes (FROMLIST/PENDING)

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #1473 - TCSR clock controller patches for glymur and x1e80100
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/29070407637

Checker Result Summary

checkpatch ⏭️ CI infrastructure failure - unable to merge PR

dt-binding-check ⏭️ CI infrastructure failure - unable to merge PR

dtb-check ⏭️ CI infrastructure failure - unable to merge PR

sparse-check ⏭️ CI infrastructure failure - unable to merge PR

check-uapi-headers ⏭️ CI infrastructure failure - unable to merge PR

check-patch-compliance ⏭️ CI infrastructure failure - unable to merge PR

tag-check ✅ All commits have valid prefixes (FROMLIST/PENDING)

⚠️ CI Infrastructure Failure

Root cause: The CI workflow failed during the merge preparation stage with "fatal: refusing to merge unrelated histories" when attempting to merge both the topic branch (topic/tech/bsp/clk) and the PR branch into the integration baseline.

Failure details:
2026-07-10T05:19:17.3263222Z  ** Merging topic branch: topic/tech/bsp/clk
2026-07-10T05:19:35.7183074Z fatal: refusing to merge unrelated histories
2026-07-10T05:19:35.8256566Z Merge failed, manual merge
...
2026-07-10T05:19:36.8386124Z Merging pr-1473 (no-commit)...
2026-07-10T05:19:56.6709132Z fatal: refusing to merge unrelated histories
2026-07-10T05:19:56.7814382Z Merge failed or conflicts detected. Aborting merge.
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 checker validation from running.

Analysis:

This is a CI infrastructure/configuration issue, not a patch quality problem. The "refusing to merge unrelated histories" error indicates that:

The PR branch (refs/pull/1473/head) does not share a common ancestor with the integration baseline (947408df47978cb86ffcd180a6244379e03301bf)

The topic branch (topic/tech/bsp/clk) also has unrelated history to the baseline

This typically occurs when:

The PR was created from a branch with a different history than the target branch

The baseline tag or topic branch references are misconfigured

The PR branch was force-pushed or rebased in a way that broke the history chain

Fix:

Since no actual checker validation ran, there are no patch-level issues to fix. The resolution requires one of:
Rebase the PR branch onto the correct baseline:
git fetch origin <target-branch>
git rebase origin/<target-branch>
git push --force-with-lease
Use --allow-unrelated-histories if the PR intentionally introduces a new history (rare):
git merge --allow-unrelated-histories <branch>
Verify the CI configuration - ensure the baseline tag and topic branch references are correct in the kernel-config workflow

Re-trigger the CI after fixing the branch history
Reproduce locally:
# Clone and attempt the same merge the CI tried
git clone https://github.com/qualcomm-linux/kernel-topics.git
cd kernel-topics
git fetch origin pull/1473/head:pr-1473
git checkout 947408df47978cb86ffcd180a6244379e03301bf
git merge pr-1473
# Will fail with: fatal: refusing to merge unrelated histories
✅ tag-check (Manual Verification)

All 7 commits in the PR have valid subject-line prefixes:

Commits 1-5: FROMLIST: (posted to mailing list)

Commits 6-7: PENDING: (work-in-progress)

Note: The PENDING: prefix is acceptable for vendor-internal branches, though check-patch-compliance would flag it if that checker had run (known limitation for vendor-only commits).

Verdict

Cannot assess patch quality - all checkers failed during CI infrastructure setup before any validation could run. The PR commits themselves appear properly formatted with correct subject prefixes. Action required: Fix the branch history issue and re-trigger CI.

qianyu-qcom added 5 commits July 3, 2026 22:20

qianyu-qcom changed the title ~~Tech/bsp/clk~~ Vote qref in tcsr driver Jul 3, 2026

qcomlnxci requested review from a team, Mike Tipton (mdtipton) and Taniya Das (taniyadas20) and removed request for a team July 3, 2026 19:57

qianyu-qcom added 2 commits July 10, 2026 12:57

qcomlnxci requested a review from a team July 10, 2026 05:02

Uh oh!

Conversation

qianyu-qcom commented Jul 3, 2026

Uh oh!

qlijarvis commented Jul 3, 2026

🔨 Build Failure Analysis — PR #1473

Verdict

Uh oh!

qlijarvis commented Jul 3, 2026

🔨 Build Failure Analysis — PR #1473

Verdict

Uh oh!

qlijarvis commented Jul 3, 2026

PR #1473 — validate-patch

Final Summary

🔍 Patch Validation

Commit Message

Diff

Issues

Verdict

Final Summary

Uh oh!

qlijarvis commented Jul 3, 2026

PR #1473 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

❌ CI Infrastructure Failure (All Checkers)

Verdict

Uh oh!

qlijarvis commented Jul 10, 2026

PR #1473 — validate-patch

Final Summary

🔍 Patch Validation

Summary by Commit

Commit 1/7: FROMLIST: dt-bindings: clock: qcom: Move glymur TCSR to own binding

Commit 2/7: FROMLIST: dt-bindings: clock: qcom,glymur-tcsr: Add mahua support

Commit 3/7: FROMLIST: clk: qcom: Add generic clkref_en support

Commit 4/7: FROMLIST: clk: qcom: tcsrcc-glymur: Add regulator

Commit 5/7: FROMLIST: clk: qcom: tcsrcc-glymur: Add Mahua QREF

Commit 6/7: PENDING: dt-bindings: clock: qcom: Move x1e80100 TCSR to own binding

Commit 7/7: PENDING: clk: qcom: tcsrcc-x1e80100: Migrate to clk_ref

Commit Message

Diff

Issues

Verdict

Final Summary

Uh oh!

qlijarvis commented Jul 10, 2026

PR #1473 — checker-log-analyzer

🤖 CI Checker Analysis (checker-log-analyzer)

⚠️ CI Infrastructure Failure

✅ tag-check (Manual Verification)

Verdict

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants