From: sashiko-bot@kernel.org
To: luoliang@kylinos.cn
Cc: sched-ext@lists.linux.dev
Subject: Re: [PATCH] sched_ext: Fix missing @slice and @vtime descriptions in finish_dispatch() kernel-doc
Date: Tue, 25 Aug 2026 05:58:49 +0000 [thread overview]
Message-ID: <20260825055849.ECF201F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260825055053.2295139-1-luoliang@kylinos.cn>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Adding kernel-doc descriptions for non-existent parameters `@slice` and `@vtime` causes an "Excess function parameter" kernel-doc warning.
--
--- Patch [1]: [PATCH] sched_ext: Fix missing @slice and @vtime descriptions in finish_dispatch() kernel-doc ---
commit 41530400fea7676e4713b34dcf07ebfd18e9b839
Author: Liang Luo <luoliang@kylinos.cn>
sched_ext: Fix missing @slice and @vtime descriptions in finish_dispatch() kernel-doc
This commit attempts to fix kernel-doc warnings by adding slice and vtime
parameter descriptions to the finish_dispatch() comment block.
> diff --git a/kernel/sched/ext/ext.c b/kernel/sched/ext/ext.c
> index 18183062f751c..84b2bb05ab90b 100644
> --- a/kernel/sched/ext/ext.c
> +++ b/kernel/sched/ext/ext.c
> @@ -2664,6 +2664,8 @@ static void dispatch_to_local_dsq(struct scx_sched *sch, struct rq *rq,
> * @p: task to finish dispatching
> * @qseq_at_dispatch: qseq when @p started getting dispatched
> * @dsq_id: destination DSQ ID
> + * @slice: slice carried by the insert verdict, 0 keeps the current value
> + * @vtime: vtime carried by the insert verdict, committed on PRIQ inserts
[Severity: Low]
Will this trigger "Excess function parameter" kernel-doc warnings?
Looking at the code, finish_dispatch() does not appear to have slice or vtime
parameters in its signature:
static void finish_dispatch(struct scx_sched *sch, struct rq *rq,
struct task_struct *p,
unsigned long qseq_at_dispatch,
u64 dsq_id, u64 enq_flags)
> * @enq_flags: %SCX_ENQ_*
> *
> * Dispatching to local DSQs may need to wait for queueing to complete or
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260825055053.2295139-1-luoliang@kylinos.cn?part=1
next prev parent reply other threads:[~2026-08-25 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 5:50 [PATCH] sched_ext: Fix missing @slice and @vtime descriptions in finish_dispatch() kernel-doc luoliang
2026-08-25 5:58 ` sashiko-bot [this message]
2026-08-25 8:00 ` Liang Luo
2026-08-31 17:31 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260825055849.ECF201F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=luoliang@kylinos.cn \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sched-ext@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox