Skip to content

FROMLIST: misc: fastrpc: Enable poll mode for specific devices#598

Open
Jianping-Li wants to merge 6 commits into
qualcomm-linux:qcom-6.18.yfrom
Jianping-Li:fastcv_fix
Open

FROMLIST: misc: fastrpc: Enable poll mode for specific devices#598
Jianping-Li wants to merge 6 commits into
qualcomm-linux:qcom-6.18.yfrom
Jianping-Li:fastcv_fix

Conversation

@Jianping-Li
Copy link
Copy Markdown

Some devices, such as Talos, do not support poll mode, and it is not appropriate to force all devices to start in poll mode in the fastrpc driver. In case poll timeout happens, the call will fallback to normal RPC mode. Poll mode can be enabled by user by using FASTRPC_IOCTL_SET_OPTION ioctl request with FASTRPC_POLL_MODE request id.

Link: https://lore.kernel.org/all/20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com/

CRs-Fixed: 4450320

@Jianping-Li Jianping-Li requested review from a team, Komal-Bajaj, quic-kaushalk and trsoni May 19, 2026 08:53
@qswat-orbit-external
Copy link
Copy Markdown

Merge Check Failed: No Change Task Found

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

Entities:

  • kernel.qli.2.0

CR: 4450320

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

@knaveen-qc
Copy link
Copy Markdown

PR #598 — validate-patch

PR: #598

Verdict Issues Detailed Report
0 Full report
Verdict: ❌ — click to expand

🔍 Patch Validation

PR: FROMLIST: misc: fastrpc: Enable poll mode for specific devices — PR #598
Upstream: https://lore.kernel.org/all/20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com/
Verdict: ❌ FAIL


Step 1 — Lore Link

Lore link found: https://lore.kernel.org/all/20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com/

PR changes files: drivers/misc/fastrpc.c, include/uapi/misc/fastrpc.h. The link points to patch 5 of a series (1622565-5) authored by Ekansh Gupta. The PR contains a single commit authored by Jianping Li.


Step 2 — Upstream Lore Patch

Network access is restricted; direct fetch via curl/b4 was not possible (exit code 6). Analysis is based on the PR patch content, the CI checker output from check-patch-compliance, and the message-ID structure.

The message-ID 20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com encodes:

  • Date: 2026-04-24
  • Series PID: 1622565
  • Patch number: 5 (of a multi-patch series)
  • Author: ekansh.gupta@oss.qualcomm.com

Step 3 — Upstream Patch Status

The lore patch was posted 2026-04-24. Network access is unavailable to query the thread for ACK/NAK signals.

Community verdict: ⏳ Decision Pending — patch posted 2026-04-24; no network access to confirm merge status. Verify manually at the lore URL.


Step 4–5 — Diff Comparison

The CI checker (check-patch-compliance) explicitly reported:

Change is different from the one mentioned in Link

This confirms the PR diff does not faithfully match lore patch 5. Based on content analysis, the PR commit appears to combine content from multiple patches in the series (patches covering the ioctl interface, the machine compatibility list, and the poll-mode logic change) into a single commit, while linking only to patch 5. The lore patch 5 subject is "Enable poll mode for specific devices" — the PR subject matches — but the diff scope is broader than a single patch in the series.


Commit Message

Check Status Note
Subject matches upstream FROMLIST: misc: fastrpc: Enable poll mode for specific devices — subject line matches lore patch 5 subject
Body preserves rationale ⚠️ Body is a condensed paraphrase; acceptable but abbreviated compared to a full lore commit body
Fixes tag present/correct N/A No Fixes: tag — this is a new feature, not a bug fix
Authorship preserved (FROMLIST: rule) FROMLIST: requires the original lore author's Signed-off-by: to be present. Lore author is Ekansh Gupta <ekansh.gupta@oss.qualcomm.com> — their Signed-off-by: is absent from the PR commit. Only Signed-off-by: Jianping Li is present.
Backport note (if applicable) N/A Not a backport

Diff

File Status Notes
drivers/misc/fastrpc.c CI checker confirmed diff differs from linked lore patch; PR appears to merge content from multiple series patches into one commit
include/uapi/misc/fastrpc.h Same — FASTRPC_IOCTL_SET_OPTION, FASTRPC_POLL_MODE, and fastrpc_ioctl_set_option struct additions may span more than one lore patch

Upstream Patch Status

Commit Community Verdict
FROMLIST: misc: fastrpc: Enable poll mode for specific devices ⏳ Decision Pending — posted 2026-04-24; network unavailable to confirm; verify at lore URL

Dependency Check

Check Status Note
Series prerequisites present ⚠️ Lore link is to patch 5 of a series; patches 1–4 (1622565-1 through 1622565-4) are not accounted for in this PR. Either they must already be in the base branch (qcom-6.18.y) or included in this PR. This must be verified.

qcom-next Presence

Commit Status
FROMLIST: misc: fastrpc: Enable poll mode for specific devices ⏭️ Skipped — no network access to fetch qcom-next; verify manually

Issues Found

  1. ❌ Diff diverges from linked lore patch — The CI check-patch-compliance checker explicitly reported "Change is different from the one mentioned in Link". The PR diff is broader than what lore patch 5 alone would contain, suggesting content from multiple series patches has been squashed into one commit without updating the Link: tag to reflect all source patches.

  2. ❌ Missing original author Signed-off-by: — For a FROMLIST: commit, the lore patch author (Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>) must appear as Signed-off-by: in the PR commit. It is absent. The CI checker also flagged: "Author mismatch: Original author: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com> / Commit author: Jianping Li <jianping.li@oss.qualcomm.com>".

  3. ⚠️ Series dependency not verified — The Link: points to patch 5 of a multi-patch series. Patches 1–4 of the same series must either already be in qcom-6.18.y or be included in this PR. This is not documented in the commit message.

  4. ⚠️ Checkpatch style warning — Block comment alignment issue at drivers/misc/fastrpc.c:1323: the * on continuation lines of the block comment is not aligned (missing leading space before *).


Recommendation

Do not merge as-is. Two blocking issues must be resolved:

  1. Fix authorship: Add Signed-off-by: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com> to the commit message (the original lore author). For FROMLIST: commits, the submitter (Jianping Li) correctly appears in From:, but the original author's Signed-off-by: is mandatory.

  2. Fix diff / Link alignment: Either (a) split the commit to match the individual lore patches and add a Link: tag for each, or (b) if this is intentionally a squash of multiple lore patches, update the commit message to include Link: tags for all source patches from the series (not just patch 5). The current single Link: pointing to patch 5 does not cover the full diff content.

  3. Verify series prerequisites: Confirm patches 1–4 of series 1622565 are already present in qcom-6.18.y, and document this in the commit message if relevant.

  4. Fix block comment style: Align the * in the multi-line block comment at drivers/misc/fastrpc.c:1323.


Final Summary

  1. Lore link present: Yes — https://lore.kernel.org/all/20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com/
  2. Lore link matches PR commits: ❌ No — CI checker confirmed diff content differs from the linked lore patch; PR diff appears to combine multiple series patches under a single Link: pointing only to patch 5
  3. Upstream patch status: ⏳ Decision Pending — posted 2026-04-24; network unavailable to confirm merge; verify at lore URL
  4. PR present in qcom-next: ⏭️ Skipped — network unavailable; verify manually

@knaveen-qc
Copy link
Copy Markdown

PR #598 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch 2 warnings in commit 66e91c42
dt-binding-check ⏭️ No changes in Documentation/devicetree/bindings
dtb-check ⏭️ No changes in Devicetree
sparse-check sparse-check.sh passed
check-uapi-headers check-uapi-headers.sh passed
check-patch-compliance Content mismatch + author mismatch
tag-check Commit subject starts with FROMLIST:
qcom-next-check N/A Target is qcom-6.18.y, not qcom-next

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: FROMLIST: misc: fastrpc: Enable poll mode for specific devices (#598)
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/26086936510
Target branch: qcom-6.18.y (tag-check is mandatory)

Checker Result Summary
checkpatch 2 warnings in commit 66e91c42
dt-binding-check ⏭️ No changes in Documentation/devicetree/bindings
dtb-check ⏭️ No changes in Devicetree
sparse-check sparse-check.sh passed
check-uapi-headers check-uapi-headers.sh passed
check-patch-compliance Content mismatch + author mismatch
tag-check Commit subject starts with FROMLIST:
qcom-next-check N/A Target is qcom-6.18.y, not qcom-next

❌ checkpatch

Root cause: Commit 66e91c428f74 has two style warnings — a long commit-description line and a misaligned block-comment *.

Failure details:

WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#8:
appropriate to force all devices to start in poll mode in the fastrpc driver.

WARNING: Block comments should align the * on each line
#94: FILE: drivers/misc/fastrpc.c:1323:
+	/*
+	* Set message context as polled if the call is for a user PD

66e91c428f74002cf0a7b420064fcfdf44c4b7c2 total: 0 errors, 2 warnings, 0 checks, 189 lines checked

Commit 66e91c428f74 ("FROMLIST: misc: fastrpc: Enable poll mode for specific devices") has style problems, please review.

Fix:

  1. COMMIT_LOG_LONG_LINE — Wrap the commit body line at 75 chars:
    appropriate to force all devices to start in poll mode in the
    fastrpc driver.
    
  2. BLOCK_COMMENT_STYLE — Align the * in the block comment at drivers/misc/fastrpc.c:1323:
    /* Before (wrong):
     /*
     * Set message context as polled if the call is for a user PD
     */
    
    /* After (correct):
     /*
      * Set message context as polled if the call is for a user PD
      */
  3. Apply via interactive rebase:
    git rebase -i <base_sha>   # mark commit as 'edit'
    # fix commit message and fastrpc.c
    git add drivers/misc/fastrpc.c
    git commit --amend
    git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --summary-file --ignore FILE_PATH_CHANGES \
  --git 6964936c9bfc3337aa8ba8a0fb25021d06e5ce04..66e91c428f74002cf0a7b420064fcfdf44c4b7c2

❌ check-patch-compliance

Root cause: The commit in the PR differs from the upstream patch at the linked lore URL, and the commit author does not match the original patch author.

Failure details:

Checking commit: FROMLIST: misc: fastrpc: Enable poll mode for specific devices
Change is different from the one mentioned in Link
Author mismatch:
  Original author: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
  Commit author : Jianping Li <jianping.li@oss.qualcomm.com>

The Link: tag points to:

https://lore.kernel.org/all/20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com/

The upstream patch was authored by Ekansh Gupta, but the PR commit is authored by Jianping Li.

Fix — two sub-issues to resolve:

  1. Author mismatch — The commit author must match the original upstream author. Fix with:

    git rebase -i <base_sha>   # mark commit as 'edit'
    git commit --amend --author="Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>"
    git rebase --continue

    If Jianping Li made local adaptations, preserve attribution using Co-developed-by: / Signed-off-by: for both authors.

  2. Content mismatch — The diff in the PR does not match the upstream mbox. Investigate the delta:

    b4 am --single-message -C -l -3 \
      https://lore.kernel.org/all/20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com/ \
      -o /tmp/out
    diff \
      <(git format-patch -1 66e91c428f74 --stdout | awk '/^diff/,/^--$/' | grep -E '^[+-][^+-]') \
      <(awk '/^diff/,/^--$/' /tmp/out/*.mbx | grep -E '^[+-][^+-]')
    • If the delta is a legitimate backport adaptation (e.g., context differences for qcom-6.18.y), document it in the commit message.
    • If there are extra or missing hunks that should not be there, align the diff with the upstream patch.

Reproduce locally:

b4 am --single-message -C -l -3 \
  https://lore.kernel.org/all/20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com/ \
  -o /tmp/out

Verdict

2 blockers before merge: fix the checkpatch block-comment style and long commit-description line, then resolve the check-patch-compliance author mismatch and content delta against the upstream lore patch.

Copy link
Copy Markdown

@shashim-quic shashim-quic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Intake review

All formal checks pass (CRs-Fixed ✓, FROMLIST ✓, Link: ✓, author/committer domains ✓).

drivers/misc/fastrpc.c — block comment style

The new comment block uses * without a leading space:

+	/*
+	* Set message context as polled if the call is for a user PD
+	* dynamic module and user has enabled poll mode.
+	*/

Kernel coding style requires a space before * in multi-line block comments:

	/*
	 * Set message context as polled if the call is for a user PD
	 * dynamic module and user has enabled poll mode.
	 */

include/uapi/misc/fastrpc.h — IOCTL macro alignment

+#define FASTRPC_IOCTL_SET_OPTION _IOWR('R', 12, struct fastrpc_ioctl_set_option)

The surrounding macros use a tab between the macro name and _IOWR. Please add a tab to align with the block:

#define FASTRPC_IOCTL_SET_OPTION	_IOWR('R', 12, struct fastrpc_ioctl_set_option)

@qswat-orbit-external
Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4450320 is not eligible for merge.

The parent software image for kernel.qli.2.0 is not development complete.

Entity: kernel.qli.2.0
CR: 4450320
Reason: CR_CANNOT_MERGE

Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations.

@qcomlnxci qcomlnxci requested a review from a team May 27, 2026 10:06
@qlijarvis
Copy link
Copy Markdown

PR #598 — validate-patch

PR: #598

Verdict Issues Detailed Report
⚠️ 0 Full report

Final Summary

  1. Lore link present: Yes — https://lore.kernel.org/all/20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com/
  2. Lore link matches PR commits: Cannot verify — network restricted; no lore fetch possible
  3. Upstream patch status: Cannot verify — network restricted; unable to check lore thread or mainline git trees
  4. PR present in qcom-next: No — qcom-next has older Feb 15 revision (352cb6c8d98d); PR is Apr 24 revision with different content (91 vs 142 insertions, adds device compatibility logic)
Verdict: ⚠️ — click to expand

🔍 Patch Validation

PR: #598 - FROMLIST: misc: fastrpc: Enable poll mode for specific devices
Upstream commit: https://lore.kernel.org/all/20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com/
Verdict: ⚠️ PARTIAL

Commit Message

Check Status Note
Subject matches upstream ⚠️ Cannot verify - network restricted; format correct for FROMLIST
Body preserves rationale Clear explanation of poll mode device compatibility
Fixes tag present/correct N/A Not a bug fix
Authorship preserved BLOCKING: Original author Ekansh Gupta missing from Signed-off-by chain
Backport note (if applicable) N/A FROMLIST prefix, not a backport

Diff

File Status Notes
drivers/misc/fastrpc.c ⚠️ 91 insertions; cannot verify against lore (network restricted)
include/uapi/misc/fastrpc.h ⚠️ 25 insertions; adds FASTRPC_IOCTL_SET_OPTION + FASTRPC_POLL_MODE

Issues

BLOCKING - Must Fix Before Merge:

  1. Missing original author's Signed-off-by — For FROMLIST: commits, the original lore patch author must appear in the Signed-off-by chain. The message-ID 20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com indicates the upstream author is Ekansh Gupta, but only Jianping Li's SOB is present.

    Fix: Add before Jianping Li's SOB:

    Signed-off-by: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
    Signed-off-by: Jianping Li <jianping.li@oss.qualcomm.com>
    

Informational:

  1. Newer upstream revision — qcom-next contains commit 352cb6c8d98d (Feb 15, 2026, lore link 20260215182136.3995111-5) with 142 insertions. This PR links to Apr 24, 2026 revision with 91 insertions, suggesting a v2+ with refined scope (adds poll_mode_supported field and platform exception list fastrpc_poll_supported_machines[]).

  2. Cannot verify diff faithfulness — Network restrictions prevent fetching the Apr 24 lore patch for line-by-line comparison.

  3. Cannot verify upstream status — Cannot check lore thread for ACK/NAK/merge signals.

Verdict

Do not merge until authorship is corrected. The missing original author SOB violates kernel contribution guidelines for FROMLIST commits. Once fixed, the commit structure and message appear sound, but full validation requires network access to lore.kernel.org.

Final Summary

  1. Lore link present: Yes — https://lore.kernel.org/all/20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com/
  2. Lore link matches PR commits: Cannot verify — network restricted; no lore fetch possible
  3. Upstream patch status: Cannot verify — network restricted; unable to check lore thread or mainline git trees
  4. PR present in qcom-next: No — qcom-next has older Feb 15 revision (352cb6c8d98d); PR is Apr 24 revision with different content (91 vs 142 insertions, adds device compatibility logic)

@qlijarvis
Copy link
Copy Markdown

PR #598 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch 2 warnings: long commit line, block comment alignment
dt-binding-check ⏭️ No DT binding changes
dtb-check ⏭️ No DTS changes
sparse-check Passed
check-uapi-headers Passed
check-patch-compliance Content mismatch + 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: #598 - FROMLIST: misc: fastrpc: Enable poll mode for specific devices
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/26504693510

Checker Result Summary
checkpatch 2 warnings: long commit line, block comment alignment
dt-binding-check ⏭️ No DT binding changes
dtb-check ⏭️ No DTS changes
sparse-check Passed
check-uapi-headers Passed
check-patch-compliance Content mismatch + author mismatch
tag-check Subject has valid FROMLIST: prefix

❌ checkpatch

Root cause: Commit body line exceeds 75 characters and block comment has misaligned asterisk.

Failure details:

WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#8: 
appropriate to force all devices to start in poll mode in the fastrpc driver.

WARNING: Block comments should align the * on each line
#96: FILE: drivers/misc/fastrpc.c:1346:
+	 * dynamic module and user has enabled poll mode.
+	*/

Fix:

  1. Long commit line — Wrap the commit body at 75 characters:

    git rebase -i b0d4b962afa7
    # mark commit as 'edit'
    git commit --amend
    # In the editor, wrap line 8:
    # "appropriate to force all devices to start in poll mode in the fastrpc driver."
    # becomes:
    # "appropriate to force all devices to start in poll mode in the"
    # "fastrpc driver."
    git rebase --continue
  2. Block comment alignment — Align the closing */ with the opening /*:

    # Edit drivers/misc/fastrpc.c:1346-1347
    # Change:
    	 * dynamic module and user has enabled poll mode.
    	*/
    # To:
    	 * dynamic module and user has enabled poll mode.
    	 */
    git add drivers/misc/fastrpc.c
    git commit --amend --no-edit

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git b0d4b962afa7..1728bb3cd716

❌ check-patch-compliance

Root cause: The patch content differs from the upstream lore link, and the commit author does not match the original patch author.

Failure details:

Checking commit: FROMLIST: misc: fastrpc: Enable poll mode for specific devices
Change is different from the one mentioned in Link
Author mismatch:
  Original author: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
  Commit author : Jianping Li <jianping.li@oss.qualcomm.com>

Fix:

  1. Author mismatch — The original patch author is Ekansh Gupta, but the commit is authored by Jianping Li. Fix the author:

    git rebase -i b0d4b962afa7
    # mark commit as 'edit'
    git commit --amend --author="Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>"
    git rebase --continue
  2. Content mismatch — Fetch the upstream patch and compare:

    b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com/ -o /tmp/upstream
    git format-patch -1 1728bb3cd716 --stdout > /tmp/pr.patch
    # Compare the diff hunks:
    diff <(awk '/^diff/,/^--$/' /tmp/pr.patch | grep -E '^[+-][^+-]') \
         <(awk '/^diff/,/^--$/' /tmp/upstream/*.mbx | grep -E '^[+-][^+-]')

    Analysis: The PR patch appears to have modifications not present in the upstream version. Common scenarios:

    • Context-only shift (line numbers changed due to base differences) → Not a real mismatch; document in commit message.
    • Legitimate adaptation (e.g., backport adjustments for older kernel) → Add a note in the commit body explaining the changes.
    • Missing/extra hunks → Verify if the changes are intentional. If the PR has additional changes not in upstream, either:
      • Remove the extra changes and match upstream exactly, OR
      • Document the delta in the commit message with a note like:
        [ Jianping: Added X for compatibility with qcom-6.18.y ]
        

Reproduce locally:

b4 am --single-message -C -l -3 https://lore.kernel.org/all/20260424095903.1622565-5-ekansh.gupta@oss.qualcomm.com/

Verdict

2 blockers must be fixed before merge:

  1. checkpatch — Fix commit body line wrapping and block comment alignment (trivial formatting fixes).
  2. check-patch-compliance — Fix author to match upstream (Ekansh Gupta) and resolve content mismatch by either matching upstream exactly or documenting the delta.

The tag-check passes (subject has FROMLIST: prefix as required for qcom-6.18.y branch). All other checkers passed or were skipped appropriately.

shashim-quic
shashim-quic previously approved these changes Jun 1, 2026
@qcomlnxci
Copy link
Copy Markdown

Test Matrix

Test Case lemans-evk monaco-evk qcs615-ride qcs6490-rb3gen2 qcs8300-ride qcs9100-ride-r3 x1e80100-crd
BT_FW_KMD_Service ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ◻️ ◻️
BT_ON_OFF ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ◻️ ◻️
BT_SCAN ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ◻️ ◻️
CPUFreq_Validation ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ◻️
CPU_affinity ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ◻️
DSP_AudioPD ✅ Pass ◻️ ⚠️ skip ◻️ ✅ Pass ◻️ ◻️
Ethernet ✅ Pass ◻️ ⚠️ 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 ◻️ ◻️
PCIe ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ◻️
Probe_Failure_Check ❌ Fail ◻️ ✅ Pass ◻️ ❌ Fail ❌ Fail ◻️
RMNET ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ◻️
UFS_Validation ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ◻️
USBHost ❌ Fail ◻️ ❌ Fail ◻️ ❌ Fail ❌ Fail ◻️
WiFi_Firmware_Driver ❌ Fail ◻️ ❌ Fail ◻️ ✅ Pass ◻️ ◻️
WiFi_OnOff ✅ Pass ◻️ ⚠️ skip ◻️ ✅ Pass ◻️ ◻️
adsp_remoteproc ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ❌ Fail ◻️
cdsp_remoteproc ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ❌ Fail ◻️
gpdsp_remoteproc ✅ Pass ◻️ ⚠️ skip ◻️ ✅ Pass ❌ Fail ◻️
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 ◻️ ◻️
remoteproc ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ❌ Fail ◻️
rngtest ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ◻️
shmbridge ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ✅ Pass ◻️
smmu ❌ Fail ◻️ ❌ Fail ◻️ ✅ Pass ❌ Fail ◻️
watchdog ✅ Pass ◻️ ✅ Pass ◻️ ✅ Pass ◻️ ◻️
wpss_remoteproc ✅ Pass ◻️ ⚠️ skip ◻️ ✅ Pass ✅ Pass ◻️

@qswat-orbit-external
Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4450320 is not eligible for merge.

The parent software image for kernel.qli.2.0 is not development complete.

Entity: kernel.qli.2.0
CR: 4450320
Reason: CR_CANNOT_MERGE

Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations.

@qcomlnxci qcomlnxci requested a review from a team June 2, 2026 09:28
@qlijarvis
Copy link
Copy Markdown

PR #598 — validate-patch

PR: #598

Verdict Issues Detailed Report
0 Full report

Final Summary

  1. Lore link present: Commits 1-2: No (reverts, expected) | Commits 3-6: Yes
  2. Lore link matches PR commits: Cannot verify (network restricted), but qcom-next presence suggests content is identical
  3. Upstream patch status: ⏳ Decision Pending — patches posted 2026-05-21, no merge signals yet
  4. PR present in qcom-next: Commits 3-6 already present with FROMLIST: prefix and correct authorship; commits 1-2 revert those commits
  5. Authorship compliance:FAIL — Original author's credit stripped from commits 3-6; missing SOB on commits 1-2

Overall verdict: ❌ FAIL — Do not merge. Authorship violation and duplicate work.

Verdict: ❌ — click to expand

🔍 Patch Validation Report

PR: #598 (6 commits)
Verdict:FAIL


Summary by Commit

Commit 1/6: Revert "FROMLIST: misc: fastrpc: Add polling mode support for fastRPC driver"

  • Upstream: N/A (revert commit)
  • Verdict: ⚠️ REVIEW — Missing Signed-off-by

Commit 2/6: Revert "FROMLIST: misc: fastrpc: Move fdlist to invoke context structure"

  • Upstream: N/A (revert commit)
  • Verdict: ⚠️ REVIEW — Missing Signed-off-by

Commit 3/6: misc: fastrpc: Move fdlist to invoke context structure

Commit 4/6: misc: fastrpc: Replace hardcoded ctxid mask with GENMASK

Commit 5/6: misc: fastrpc: Expand context ID mask for DSP polling

Commit 6/6: misc: fastrpc: Add polling mode support for fastRPC


Commit Message Analysis

Check Commits 1-2 (Reverts) Commits 3-6 (FROMLIST) Status
Subject matches upstream N/A ✅ Yes PASS
Body preserves rationale ⚠️ Minimal ✅ Yes PARTIAL
Fixes tag present/correct N/A N/A N/A
Authorship preserved ❌ No SOB FAIL FAIL
Backport note N/A N/A N/A

Authorship Issues (CRITICAL)

Commits 3-6 violate authorship requirements:

Per kernel contribution guidelines and the validate-patch skill:

  • These commits lack a vendor prefix (UPSTREAM:, BACKPORT:, FROMLIST:, etc.)
  • Without a prefix, the From: field must match the lore patch author
  • The original author's Signed-off-by: must be present

Current state in qcom-next:

c75022aae239 FROMLIST: misc: fastrpc: Move fdlist to invoke context structure
0a6e64c0f0f7 FROMLIST: misc: fastrpc: Replace hardcoded ctxid mask with GENMASK
db409f4e2598 FROMLIST: misc: fastrpc: Expand context ID mask for DSP polling mode support
352cb6c8d98d FROMLIST: misc: fastrpc: Add polling mode support for fastRPC driver

These commits already exist in qcom-next with the FROMLIST: prefix and correct authorship.


Diff Comparison

Cannot verify diff faithfulness without network access to fetch lore patches. However, based on qcom-next presence:

File Status Notes
drivers/misc/fastrpc.c ⏭️ Skipped Network restricted; cannot fetch lore patches for comparison
include/uapi/misc/fastrpc.h ⏭️ Skipped Network restricted; cannot fetch lore patches for comparison

Upstream Patch Status

Commit Community Verdict
Commit 3 Decision Pending — Posted to lore.kernel.org on 2026-05-21; no merge signals found yet
Commit 4 Decision Pending — Posted to lore.kernel.org on 2026-05-21; no merge signals found yet
Commit 5 Decision Pending — Posted to lore.kernel.org on 2026-05-21; no merge signals found yet
Commit 6 Decision Pending — Posted to lore.kernel.org on 2026-05-21; no merge signals found yet

Note: Network access restricted; cannot fetch lore threads to verify acceptance/rejection signals.


qcom-next Presence

Commit Status
Commit 1 (Revert) ⚠️ Reverts dba4eb255febb which exists in qcom-next
Commit 2 (Revert) ⚠️ Reverts 318d871b124f which exists in qcom-next
Commit 3 Already present as c75022aae239 with FROMLIST: prefix
Commit 4 Already present as 0a6e64c0f0f7 with FROMLIST: prefix
Commit 5 Already present as db409f4e2598 with FROMLIST: prefix
Commit 6 Already present as 352cb6c8d98d with FROMLIST: prefix

Issues Found

1. Authorship Violation (Commits 3-6)

Commits 3-6 change the author from the original lore patch author (Ekansh Gupta) to a different person (Jianping Li) without:

  • Adding a vendor prefix (FROMLIST:, BACKPORT:, etc.)
  • Preserving the original author's Signed-off-by: tag

Kernel contribution rules require:

  • If no prefix: From: must match lore author
  • If FROMLIST: prefix: Original author's Signed-off-by: must be present

Current PR violates both rules.

2. Missing Signed-off-by (Commits 1-2)

Revert commits lack any Signed-off-by: tag. All commits must have at least one SOB from the committer.

3. Duplicate Work

Commits 3-6 are already in qcom-next with the correct FROMLIST: prefix and authorship. This PR:

  • Reverts the existing FROMLIST commits (commits 1-2)
  • Re-applies them without the FROMLIST prefix (commits 3-6)
  • Changes authorship in the process

This appears to be an attempt to claim authorship of someone else's work.

4. Inconsistent Commit Message (Commit 5)

  • PR subject: "misc: fastrpc: Expand context ID mask for DSP polling"
  • qcom-next subject: "misc: fastrpc: Expand context ID mask for DSP polling mode support"

Minor wording difference; likely acceptable but should match exactly.


Recommendation

❌ REJECT this PR immediately.

Reasons:

  1. Authorship fraud: Commits 3-6 strip the original author's credit and replace it with a different author without proper attribution
  2. Duplicate commits: All four commits already exist in qcom-next with correct authorship
  3. Missing SOB tags: Reverts lack required sign-off
  4. Unnecessary churn: Reverting and re-applying identical commits serves no technical purpose

Required actions:

  1. Close this PR — do not merge under any circumstances
  2. Investigate: Determine why Jianping Li attempted to re-author Ekansh Gupta's commits
  3. If the goal was to update commit messages or fix issues:
    • Work with the original author (Ekansh Gupta)
    • Use git commit --amend --author to preserve authorship
    • Add Co-developed-by: if Jianping Li made substantial changes
    • Keep the FROMLIST: prefix until patches are merged upstream

Correct workflow for FROMLIST commits:

FROMLIST: <subject>

<body>

Link: https://lore.kernel.org/...
Signed-off-by: Original Author <original@email.com>
[Signed-off-by: Co-developer <co-dev@email.com>]  # Only if substantial changes
Signed-off-by: Submitter <submitter@email.com>

Final Summary

  1. Lore link present: Commits 1-2: No (reverts, expected) | Commits 3-6: Yes
  2. Lore link matches PR commits: Cannot verify (network restricted), but qcom-next presence suggests content is identical
  3. Upstream patch status: ⏳ Decision Pending — patches posted 2026-05-21, no merge signals yet
  4. PR present in qcom-next: Commits 3-6 already present with FROMLIST: prefix and correct authorship; commits 1-2 revert those commits
  5. Authorship compliance:FAIL — Original author's credit stripped from commits 3-6; missing SOB on commits 1-2

Overall verdict: ❌ FAIL — Do not merge. Authorship violation and duplicate work.

@qlijarvis
Copy link
Copy Markdown

PR #598 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch 2 commits missing Signed-off-by:
dt-binding-check ⏭️ No DT binding changes
dtb-check ⏭️ No DTS changes
sparse-check Passed
check-uapi-headers Passed
check-patch-compliance All 6 commits missing required prefix
tag-check All 6 commits missing required prefix

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #598 - fastrpc polling mode patches
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/26810983877
Target branch: qcom-6.18.y

Checker Result Summary
checkpatch 2 commits missing Signed-off-by:
dt-binding-check ⏭️ No DT binding changes
dtb-check ⏭️ No DTS changes
sparse-check Passed
check-uapi-headers Passed
check-patch-compliance All 6 commits missing required prefix
tag-check All 6 commits missing required prefix

❌ checkpatch

Root cause: Two Revert commits are missing Signed-off-by: trailer lines.

Failure details:

Commit 8322c30a35bd ("Revert "FROMLIST: misc: fastrpc: Add polling mode support for fastRPC driver"")
ERROR: Missing Signed-off-by: line(s)

Commit a0ab59cf2eca ("Revert "FROMLIST: misc: fastrpc: Move fdlist to invoke context structure"")
ERROR: Missing Signed-off-by: line(s)

Fix:

git rebase -i b7cce9a3884a873855693af8591d4c9c469cd17e
# Mark commits 8322c30a35bd and a0ab59cf2eca as 'edit'
# For each commit:
git commit --amend --signoff --no-edit
git rebase --continue

Reproduce locally:

./scripts/checkpatch.pl --strict --ignore FILE_PATH_CHANGES --git b7cce9a3884a873855693af8591d4c9c469cd17e..37e6136c3a460132c9f4faa2437761a57127b318

❌ check-patch-compliance

Root cause: All 6 commits have subject lines that do not start with a required prefix (FROMLIST:, FROMGIT:, UPSTREAM:, or BACKPORT:).

Failure details:

Checking commit: Revert "FROMLIST: misc: fastrpc: Add polling mode support for fastRPC driver"
Commit summary does not start with a required prefix

Checking commit: Revert "FROMLIST: misc: fastrpc: Move fdlist to invoke context structure"
Commit summary does not start with a required prefix

Checking commit: misc: fastrpc: Move fdlist to invoke context structure
Commit summary does not start with a required prefix

Checking commit: misc: fastrpc: Replace hardcoded ctxid mask with GENMASK
Commit summary does not start with a required prefix

Checking commit: misc: fastrpc: Expand context ID mask for DSP polling mode support
Commit summary does not start with a required prefix

Checking commit: misc: fastrpc: Add polling mode support for fastRPC driver
Commit summary does not start with a required prefix

Analysis:

  • Commits 1-2 (Revert commits): Subject starts with Revert "FROMLIST: ... but the checker requires a prefix before the word Revert. The correct format is UPSTREAM: Revert "FROMLIST: ..." or FROMLIST: Revert "FROMLIST: ...".
  • Commits 3-6 (regular commits): Subject starts with misc: fastrpc: with no prefix at all.

Fix:

git rebase -i b7cce9a3884a873855693af8591d4c9c469cd17e
# For each commit, mark as 'reword' and update the subject:

# Commit 1:
UPSTREAM: Revert "FROMLIST: misc: fastrpc: Add polling mode support for fastRPC driver"

# Commit 2:
UPSTREAM: Revert "FROMLIST: misc: fastrpc: Move fdlist to invoke context structure"

# Commits 3-6: Choose the appropriate prefix based on patch origin:
# - If posted to lore.kernel.org → FROMLIST:
# - If in a maintainer tree → FROMGIT:
# - If merged into Linus's tree → UPSTREAM:
# - If backported with modifications → BACKPORT:

# Example for commit 3:
FROMLIST: misc: fastrpc: Move fdlist to invoke context structure

Note: If these patches are posted upstream, add Link: <lore-url> to the commit body as well.


❌ 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 valid prefix tag. All 6 commits are missing this requirement.

Failure details:

The required prefix tags are: FROMLIST:, FROMGIT:, UPSTREAM:, BACKPORT:, QCLINUX:, PENDING:, or WORKAROUND:.

Current commit subjects:

  1. Revert "FROMLIST: misc: fastrpc: Add polling mode support for fastRPC driver" — missing prefix before Revert
  2. Revert "FROMLIST: misc: fastrpc: Move fdlist to invoke context structure" — missing prefix before Revert
  3. misc: fastrpc: Move fdlist to invoke context structure — no prefix
  4. misc: fastrpc: Replace hardcoded ctxid mask with GENMASK — no prefix
  5. misc: fastrpc: Expand context ID mask for DSP polling mode support — no prefix
  6. misc: fastrpc: Add polling mode support for fastRPC driver — no prefix

Fix:

Same fix as check-patch-compliance above — add the appropriate prefix to each commit subject. The difference is that tag-check accepts a broader set of prefixes including QCLINUX:, PENDING:, and WORKAROUND:, while check-patch-compliance only accepts upstream-linkable prefixes.

Choose the correct prefix based on patch origin:

  • Posted to lore but not yet merged → FROMLIST:
  • In a maintainer tree → FROMGIT:
  • Merged into Linus's tree → UPSTREAM:
  • Backported with modifications → BACKPORT:
  • Vendor-only, no upstream → QCLINUX:
  • Work-in-progress, not posted → PENDING:
  • Temporary fix, not for upstream → WORKAROUND:

For Revert commits, the prefix goes before the word Revert:

UPSTREAM: Revert "FROMLIST: misc: fastrpc: ..."

Reproduce locally:

git log b7cce9a3884a873855693af8591d4c9c469cd17e..37e6136c3a460132c9f4faa2437761a57127b318 --format="%H %s" | while read sha subject; do
  if ! echo "$subject" | grep -qE '^(FROMLIST|FROMGIT|UPSTREAM|BACKPORT|QCLINUX|PENDING|WORKAROUND):' &&
     ! echo "$subject" | grep -qE '^(FROMLIST|FROMGIT|UPSTREAM|BACKPORT|QCLINUX|PENDING|WORKAROUND): Revert'; then
    echo "MISSING prefix: $sha $subject"
  fi
done

Verdict

3 blockers must be fixed before merge:

  1. Add Signed-off-by: to commits 1 and 2 (checkpatch blocker)
  2. Add required prefix to all 6 commit subjects (check-patch-compliance + tag-check blocker)
    • Commits 1-2: Add prefix before Revert (e.g., UPSTREAM: Revert "FROMLIST: ...")
    • Commits 3-6: Add appropriate prefix based on patch origin (e.g., FROMLIST:, UPSTREAM:, etc.)

Recommended action: Rebase the PR to fix all commit messages in one pass:

git rebase -i b7cce9a3884a873855693af8591d4c9c469cd17e
# Mark commits 1-2 as 'edit' (to add Signed-off-by)
# Mark all 6 commits as 'reword' (to add prefix)

… driver"

This reverts commit dba4eb2.

Signed-off-by: Jianping Li <jianping.li@oss.qualcomm.com>
…ure"

This reverts commit 318d871.

Signed-off-by: Jianping Li <jianping.li@oss.qualcomm.com>
The fdlist is currently part of the meta buffer which is set during
fastrpc_get_args(), this fdlist is getting recalculated during
fastrpc_put_args().

Move fdlist to the invoke context structure to improve maintainability
and reduce redundancy. This centralizes its handling and simplifies
meta buffer preparation and reading logic.

Link: https://lore.kernel.org/all/20260521054539.128651-2-ekansh.gupta@oss.qualcomm.com/
Signed-off-by: Jianping Li <jianping.li@oss.qualcomm.com>
Replace the hardcoded context ID mask (0xFF0) with GENMASK(11, 4) to
improve readability and follow kernel bitfield conventions. Use
FIELD_PREP and FIELD_GET instead of manual shifts for setting and
extracting ctxid values.

Link: https://lore.kernel.org/all/20260521054539.128651-3-ekansh.gupta@oss.qualcomm.com/
Signed-off-by: Jianping Li <jianping.li@oss.qualcomm.com>
…support

Current FastRPC context uses a 12-bit mask:
  [ID(8 bits)][PD type(4 bits)] = GENMASK(11, 4)

This works for normal calls but fails for DSP polling mode.
Polling mode expects a 16-bit layout:
  [15:8] = context ID (8 bits)
  [7:5]  = reserved
  [4]    = async mode bit
  [3:0]  = PD type (4 bits)

If async bit (bit 4) is set, DSP disables polling. With current
mask, odd IDs can set this bit, causing DSP to skip poll updates.

Update FASTRPC_CTXID_MASK to GENMASK(15, 8) so IDs occupy upper
byte and lower byte is left for DSP flags and PD type.

Reserved bits remain unused. This change is compatible with
polling mode and does not break non-polling behavior.

Bit layout:
  [15:8] = CCCCCCCC (context ID)
  [7:5]  = xxx (reserved)
  [4]    = A (async mode)
  [3:0]  = PPPP (PD type)

Link: https://lore.kernel.org/all/20260521054539.128651-4-ekansh.gupta@oss.qualcomm.com/
Signed-off-by: Jianping Li <jianping.li@oss.qualcomm.com>
For any remote call to DSP, after sending an invocation message,
fastRPC driver waits for glink response and during this time the
CPU can go into low power modes. This adds latency to overall fastrpc
call as CPU wakeup and scheduling latencies are included. Add polling
mode support with which fastRPC driver will poll continuously on a
memory after sending a message to remote subsystem which will eliminate
CPU wakeup and scheduling latencies and reduce fastRPC overhead. In case
poll timeout happens, the call will fallback to normal RPC mode.  Poll
mode can be enabled by user by using FASTRPC_IOCTL_SET_OPTION ioctl
request with FASTRPC_POLL_MODE request id.

Link: https://lore.kernel.org/all/20260521054539.128651-5-ekansh.gupta@oss.qualcomm.com/
Signed-off-by: Jianping Li <jianping.li@oss.qualcomm.com>
@qswat-orbit-external
Copy link
Copy Markdown

Merge Check Failed: CR Not Eligible for Merge

CR 4450320 is not eligible for merge.

The parent software image for kernel.qli.2.0 is not development complete.

Entity: kernel.qli.2.0
CR: 4450320
Reason: CR_CANNOT_MERGE

Please ensure the CR passes both CCT (ComponentChangeTasks) and ICT (Integration Change Tasks) validations.

@qlijarvis
Copy link
Copy Markdown

PR #598 — validate-patch

PR: #598

Verdict Issues Detailed Report
0 Full report

Final Summary

  1. Lore link present: Yes for patches 3-6 (FROMLIST); No for patches 1-2 (reverts - not expected)

  2. Lore link matches PR commits: Cannot verify - lore links point to future date (2026-05-21), suggesting patches may not be posted upstream yet or dates are incorrect

  3. Upstream patch status: Unknown - cannot access future lore links. The FROMLIST prefix indicates patches are intended for upstream but may not be posted yet.

  4. PR present in qcom-next: Not checked - validation scope limited to commit message and authorship correctness per instructions

Recommendation: Do not merge until authorship is corrected and revert justifications are added. Verify that upstream patches are actually posted before using FROMLIST prefix.

Verdict: ❌ — click to expand

🔍 Patch Validation

PR: #598
Upstream commits: Multiple FROMLIST patches from lore.kernel.org
Verdict: ❌ FAIL

Summary

This PR contains 6 commits:

  • Patches 1-2: Revert commits (no lore links - expected for reverts)
  • Patches 3-6: FROMLIST patches with lore links to a future patch series (2026-05-21)

Commit Message Analysis

Commit Check Status Note
1/6 Revert format Proper revert commit format
1/6 Revert justification No explanation why reverting
2/6 Revert format Proper revert commit format
2/6 Revert justification No explanation why reverting
3/6 Subject matches pattern FROMLIST prefix present
3/6 Body preserves rationale Clear explanation of change
3/6 Lore link present Link included
3/6 Authorship preserved Original author not preserved
4/6 Subject matches pattern FROMLIST prefix present
4/6 Body has typo ⚠️ Says "0xFF0" should be "0xFF00"
4/6 Lore link present Link included
4/6 Authorship preserved Original author not preserved
5/6 Subject matches pattern FROMLIST prefix present
5/6 Body preserves rationale Detailed technical explanation
5/6 Lore link present Link included
5/6 Authorship preserved Original author not preserved
6/6 Subject matches pattern FROMLIST prefix present
6/6 Body preserves rationale Clear explanation of feature
6/6 Lore link present Link included
6/6 Authorship preserved Original author not preserved

Issues

Critical Issues:

  1. Authorship Not Preserved (Patches 3-6)

    • All FROMLIST patches are authored by Jianping Li <jianping.li@oss.qualcomm.com>
    • Lore links show original author is ekansh.gupta@oss.qualcomm.com
    • Missing From: tag in commit body to preserve original authorship
    • Only has Signed-off-by: Jianping Li - should have original author's SOB first
    • Fix: Add From: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com> in commit body and preserve original SOB chain
  2. Revert Commits Lack Justification (Patches 1-2)

    • Reverts commit dba4eb255febb4cc38d2e340978c58f8f21ff6cc and 318d871b124f204199bf3bf1b88d8ace436b44e6
    • No explanation of why these commits are being reverted
    • Immediately re-applies similar changes in patches 3-6
    • Fix: Add explanation like "Reverting to reapply with updated version from upstream review"

Minor Issues:

  1. Typo in Commit Message (Patch 4/6)

    • Commit message says: "Replace the hardcoded context ID mask (0xFF0)"
    • Should say: "Replace the hardcoded context ID mask (0xFF00)"
    • The actual code change is correct (replacing 0xFF00)
  2. Lore Links Point to Future Date

    • All lore links reference patches dated 2026-05-21
    • Current date context is 2026-06-04
    • Links cannot be validated as they reference future submissions
    • This suggests the patches may not actually be posted upstream yet

Diff Analysis

Cannot validate diff faithfulness without access to upstream patches (lore links point to future date). However, the code changes appear internally consistent:

File Status Notes
drivers/misc/fastrpc.c ⚠️ Cannot verify against upstream - future lore links
include/uapi/misc/fastrpc.h ⚠️ Cannot verify against upstream - future lore links

Verdict

REJECT - Critical authorship issues must be fixed before merge.

Required Fixes:

  1. Preserve original authorship for patches 3-6:

    From: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
    
    [commit message body]
    
    Link: https://lore.kernel.org/...
    Signed-off-by: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
    Signed-off-by: Jianping Li <jianping.li@oss.qualcomm.com>
    
  2. Add revert justification to patches 1-2:

    This reverts commit dba4eb255febb4cc38d2e340978c58f8f21ff6cc.
    
    Reverting to reapply with updated version incorporating upstream
    review feedback from v2 patch series.
    
  3. Fix typo in patch 4/6: Change "0xFF0" to "0xFF00" in commit message

Final Summary

  1. Lore link present: Yes for patches 3-6 (FROMLIST); No for patches 1-2 (reverts - not expected)

  2. Lore link matches PR commits: Cannot verify - lore links point to future date (2026-05-21), suggesting patches may not be posted upstream yet or dates are incorrect

  3. Upstream patch status: Unknown - cannot access future lore links. The FROMLIST prefix indicates patches are intended for upstream but may not be posted yet.

  4. PR present in qcom-next: Not checked - validation scope limited to commit message and authorship correctness per instructions

Recommendation: Do not merge until authorship is corrected and revert justifications are added. Verify that upstream patches are actually posted before using FROMLIST prefix.

@qlijarvis
Copy link
Copy Markdown

PR #598 — checker-log-analyzer

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

Checker Result Summary
Checker Result Summary
checkpatch All 6 commits pass checkpatch
dt-binding-check ⏭️ No DT binding changes
dtb-check ⏭️ No devicetree changes
sparse-check No new sparse warnings in fastrpc.c
check-uapi-headers All 933 UAPI headers backwards compatible
check-patch-compliance 3 blockers: missing prefix on reverts, author mismatch, diff mismatch
tag-check N/A Not applicable for qcom-6.18.y
qcom-next-check N/A Not applicable for qcom-6.18.y

Detailed report: Full report

Checker analysis — click to expand

🤖 CI Checker Analysis (checker-log-analyzer)

PR: #598 - Revert and reapply fastrpc polling mode patches
Source: https://github.com/qualcomm-linux/kernel-config/actions/runs/26941910274

Checker Result Summary
checkpatch All 6 commits pass checkpatch
dt-binding-check ⏭️ No DT binding changes
dtb-check ⏭️ No devicetree changes
sparse-check No new sparse warnings in fastrpc.c
check-uapi-headers All 933 UAPI headers backwards compatible
check-patch-compliance 3 blockers: missing prefix on reverts, author mismatch, diff mismatch
tag-check N/A Not applicable for qcom-6.18.y
qcom-next-check N/A Not applicable for qcom-6.18.y

❌ check-patch-compliance

Root cause: Three distinct compliance violations across 6 commits

Failure details:

1. Missing subject prefix on revert commits (2 commits):

Checking commit: Revert "FROMLIST: misc: fastrpc: Add polling mode support for fastRPC driver"
Commit summary does not start with a required prefix

Checking commit: Revert "FROMLIST: misc: fastrpc: Move fdlist to invoke context structure"
Commit summary does not start with a required prefix

2. Author mismatch (4 FROMLIST commits):

Checking commit: FROMLIST: misc: fastrpc: Move fdlist to invoke context structure
Author mismatch:
  Original author: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
  Commit author : Jianping Li <jianping.li@oss.qualcomm.com>

[Same issue for commits 4, 5, and 6]

3. Diff mismatch (2 commits):

Checking commit: FROMLIST: misc: fastrpc: Replace hardcoded ctxid mask with GENMASK
Change is different from the one mentioned in Link

Checking commit: FROMLIST: misc: fastrpc: Add polling mode support for fastRPC driver
Change is different from the one mentioned in Link

Fix:

For revert commits (commits 1 & 2):
Add the Revert: prefix to subject lines:

Revert: FROMLIST: misc: fastrpc: Add polling mode support for fastRPC driver
Revert: FROMLIST: misc: fastrpc: Move fdlist to invoke context structure

For author mismatch (commits 3-6):
Preserve the original author using git commit --amend --author="Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>" or use git cherry-pick -x when applying from lore, then add your Signed-off-by as co-developer.

For diff mismatch (commits 4 & 6):
The local changes differ from the upstream lore patches. Either:

  • Use b4 am + git am to apply the exact upstream patches, OR
  • If intentional modifications were made, document them in the commit message with a note like "[ Jianping: adapted for qcom-6.18.y context ]"

Reproduce locally:

cd kernel
git log --oneline 32eb26c08e43..94671ce8cb87
# Check each commit
for sha in $(git rev-list 32eb26c08e43..94671ce8cb87); do
  echo "=== Checking $sha ==="
  # Verify subject prefix
  git log -1 --format=%s $sha
  # Verify author
  git log -1 --format="Author: %an <%ae>" $sha
  # For FROMLIST commits, compare with lore
  link=$(git log -1 --format=%b $sha | grep "^Link:" | awk '{print $2}')
  if [ -n "$link" ]; then
    echo "Comparing with $link"
    b4 am -o /tmp/upstream.mbox "$link"
  fi
done

Verdict

3 blockers must be fixed before merge:

  1. Add Revert: prefix to 2 revert commit subjects
  2. Preserve original author (Ekansh Gupta) on 4 FROMLIST commits
  3. Reconcile diff mismatches on 2 commits (either reapply from lore or document changes)

All other checkers (checkpatch, sparse, UAPI) passed successfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants