Update README

[sgaud-quic]

No description provided.

[quic-khuzuri]

PR #12 — validate-patch

PR: #12

Verdict	Issues	Detailed Report
❌	3	pr_only_validate_patch_detailed.md

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: Update README (#12)
Upstream commit: N/A — no lore.kernel.org link found
Verdict: ❌ FAIL

Commit Message

Check	Status	Note
Subject matches upstream	❌	No upstream reference to compare against
Body preserves rationale	❌	Commit body is empty — no rationale provided
Fixes tag present/correct	❌	No Fixes: tag present
Authorship preserved	❌	Cannot verify — no upstream source identified
Backport note (if applicable)	❌	No prefix (UPSTREAM:, FROMLIST:, BACKPORT:, etc.) and no backport note

Diff

File	Status	Notes
README	❌	Cannot validate — no lore.kernel.org upstream to compare against

Issues

• No lore.kernel.org link: The commit message contains no Link: https://lore.kernel.org/... line and no recognized vendor prefix (UPSTREAM:, FROMLIST:, BACKPORT:, FROMGIT:, QCLINUX:, PENDING:, WORKAROUND:). This skill can only validate patches that carry an upstream lore reference.
• No commit prefix: Every commit in this tree must carry one of the standard prefixes to declare its provenance. This commit has none, making its origin and intent ambiguous.
• Empty commit body: The commit message contains only a subject line and a Signed-off-by:. There is no description of what changed or why, which is required for kernel contributions.
• Trivial/non-kernel change: The diff changes "Linux kernel" → "Test Linux kernel" in the top-level README. This is not a legitimate kernel patch and has no upstream equivalent.

Verdict

Reject: the patch carries no lore.kernel.org link, no recognized commit prefix, and no rationale — it cannot be validated against any upstream source and does not represent a legitimate kernel contribution.

[quic-khuzuri]

PR #12 — checker-log-analyzer

PR: #12
Checker run: https://github.com/qualcomm-linux-stg/kernel-config-test/actions/runs/25478942452

Checker	Result	Summary
Checker	Result	Summary
checkpatch	❌	Merge conflict during integration — checker never ran
dt-binding-check	❌	Merge conflict during integration — checker never ran
dtb-check	❌	Merge conflict during integration — checker never ran
sparse-check	❌	Merge conflict during integration — checker never ran
check-uapi-headers	❌	Merge conflict during integration — checker never ran
check-patch-compliance	❌	Merge conflict during integration — checker never ran
tag-check	❌	Commit subject "Update README" has no required prefix
qcom-next-check	⏭️	No FROMLIST:/UPSTREAM: commits — skipped

Detailed report: pr_only_checker_log_detailed.md

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #12 — "Update README" (qualcomm-linux-stg/kernel-topics)
Commit: 5aee43d939c4932c62b8987b6507d48d8ca949a7
Target branch: tech/all/dt/qcs9100
Source: https://github.com/qualcomm-linux-stg/kernel-config-test/actions/runs/25478942452

Checker	Result	Summary
checkpatch	❌	Merge conflict during integration — checker never ran
dt-binding-check	❌	Merge conflict during integration — checker never ran
dtb-check	❌	Merge conflict during integration — checker never ran
sparse-check	❌	Merge conflict during integration — checker never ran
check-uapi-headers	❌	Merge conflict during integration — checker never ran
check-patch-compliance	❌	Merge conflict during integration — checker never ran
tag-check	❌	Commit subject "Update README" has no required prefix
qcom-next-check	⏭️	No FROMLIST:/UPSTREAM: commits — skipped

---

❌ All Six GHA Checkers — Merge Conflict During Integration (Sync Step)

Root cause: Every checker job fails at the sync step — before any checker logic runs — because the PR's topic branch (topic/tech/all/dt/qcs9100) conflicts with the current baseline when the CI tries to build the integration branch.

Failure details:

** Merging topic branch: topic/tech/all/dt/qcs9100
Auto-merging Documentation/devicetree/bindings/arm/qcom.yaml
CONFLICT (content): Merge conflict in Documentation/devicetree/bindings/arm/qcom.yaml
Auto-merging arch/arm64/boot/dts/qcom/lemans-ride-common.dtsi
CONFLICT (content): Merge conflict in arch/arm64/boot/dts/qcom/lemans-ride-common.dtsi
Auto-merging arch/arm64/boot/dts/qcom/lemans.dtsi
CONFLICT (content): Merge conflict in arch/arm64/boot/dts/qcom/lemans.dtsi
Automatic merge failed; fix conflicts and then commit the result.
Merge failed, manual merge
##[error]Process completed with exit code 1.

Three files conflict against the baseline (27507852413bd8ba6205a95a4a1df15e62b88009):

• Documentation/devicetree/bindings/arm/qcom.yaml
• arch/arm64/boot/dts/qcom/lemans-ride-common.dtsi
• arch/arm64/boot/dts/qcom/lemans.dtsi

Important context: The PR patch itself only touches README (a one-line change). The conflicting files are in the topic branch topic/tech/all/dt/qcs9100 that this PR is associated with — meaning the topic branch has diverged from the current baseline and needs to be rebased.

Fix:

# Rebase the topic branch onto the current baseline
git fetch origin
git checkout topic/tech/all/dt/qcs9100
git rebase 27507852413bd8ba6205a95a4a1df15e62b88009
# Resolve conflicts in:
#   Documentation/devicetree/bindings/arm/qcom.yaml
#   arch/arm64/boot/dts/qcom/lemans-ride-common.dtsi
#   arch/arm64/boot/dts/qcom/lemans.dtsi
git add <resolved files>
git rebase --continue
git push --force-with-lease origin topic/tech/all/dt/qcs9100

Reproduce locally:

git checkout -b integ 27507852413bd8ba6205a95a4a1df15e62b88009
git merge topic/tech/all/dt/qcs9100
# Observe the three-way conflict

---

❌ tag-check — Missing Subject Prefix

Root cause: The single commit's subject line "Update README" does not start with any of the required prefix tags (FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, QCLINUX:, PENDING:, WORKAROUND:). The target branch tech/all/dt/qcs9100 is not qcom-next or qcom-next-staging, so the prefix is mandatory.

Failure details:

Commit 5aee43d939c4932c62b8987b6507d48d8ca949a7 ("Update README"):
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:

git rebase -i <base_sha>   # mark the commit as 'edit'
git commit --amend -m "QCLINUX: Update README"
# (or PENDING: if this is a WIP; UPSTREAM: if it mirrors an upstream commit)
git rebase --continue
git push --force-with-lease

Choose the prefix that matches the patch origin:

• QCLINUX: — if this is a vendor-only README change with no upstream equivalent
• UPSTREAM: — if this mirrors a commit already merged into Linus's tree
• PENDING: — if this is a work-in-progress not yet posted upstream

---

⏭️ qcom-next-check — Skipped

No FROMLIST: or UPSTREAM: commits in this PR — qcom-next presence check does not apply.

---

Verdict

2 distinct blockers to fix before CI can pass:

1. Merge conflict (blocker for all 6 GHA checkers): Rebase topic/tech/all/dt/qcs9100 onto the current baseline to resolve conflicts in Documentation/devicetree/bindings/arm/qcom.yaml, arch/arm64/boot/dts/qcom/lemans-ride-common.dtsi, and arch/arm64/boot/dts/qcom/lemans.dtsi. Once the topic branch is rebased and force-pushed, all six checkers will be able to run.

2. Missing subject prefix (tag-check): Amend the commit subject from "Update README" to include a valid prefix (e.g. QCLINUX: Update README).