From: Andrea Righi <arighi@nvidia.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
bpf@vger.kernel.org
Subject: Re: [PATCH] sched_ext: fix kernel-doc warnings
Date: Sat, 11 Jan 2025 18:30:26 +0100 [thread overview]
Message-ID: <Z4Kqso6hS2vsFdIt@gpd3> (raw)
In-Reply-To: <5faf8551-d434-4e2e-980b-0ff5831d3db2@infradead.org>
On Sat, Jan 11, 2025 at 09:27:27AM -0800, Randy Dunlap wrote:
...
> >> @@ -1408,7 +1409,6 @@ static struct task_struct *scx_task_iter
> >> /**
> >> * scx_task_iter_next_locked - Next non-idle task with its rq locked
> >> * @iter: iterator to walk
> >> - * @include_dead: Whether we should include dead tasks in the iteration
> >> *
> >> * Visit the non-idle task with its rq lock held. Allows callers to specify
> >> * whether they would like to filter out dead tasks. See scx_task_iter_start()
> >> @@ -3132,6 +3132,7 @@ static struct task_struct *pick_task_scx
> >> * scx_prio_less - Task ordering for core-sched
> >> * @a: task A
> >> * @b: task B
> >> + * @in_fi: in forced idle state
> >
> > in_fi is currently not used / not passed to ops.core_sched_before(), should
> > we metion this? Like appending (unused) or similar to the description?
>
> Hi Andrea,
> I'm not sure that anyone would update that comment if it did become used ;(
> so I think it's OK not to mention that.
Yeah, good point (sadly). Then the patch looks good as it is to me. :)
-Andrea
next prev parent reply other threads:[~2025-01-11 17:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 6:31 [PATCH] sched_ext: fix kernel-doc warnings Randy Dunlap
2025-01-11 9:45 ` Andrea Righi
2025-01-11 17:27 ` Randy Dunlap
2025-01-11 17:30 ` Andrea Righi [this message]
2025-01-13 18:24 ` 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=Z4Kqso6hS2vsFdIt@gpd3 \
--to=arighi@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=tj@kernel.org \
--cc=void@manifault.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.