All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Righi <arighi@nvidia.com>
To: luoliang@kylinos.cn
Cc: Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>,
	sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Fix typo in scx_bpf_dsq_insert() comment
Date: Thu, 9 Jul 2026 22:23:08 +0200	[thread overview]
Message-ID: <alADLIDIRHm3Zwyc@gpd4> (raw)
In-Reply-To: <20260709080205.534892-1-luoliang@kylinos.cn>

Hi Liang,

On Thu, Jul 09, 2026 at 04:02:05PM +0800, luoliang@kylinos.cn wrote:
> From: Liang Luo <luoliang@kylinos.cn>
> 
> The comment for scx_bpf_dsq_insert() references "@dsp_id" in the
> description body, but the parameter is named "@dsq_id" in both the
> parameter list and the function signature.
> 
> Signed-off-by: Liang Luo <luoliang@kylinos.cn>

Yep, that's a typo.

Acked-by: Andrea Righi <arighi@nvidia.com>

Thanks,
-Andrea

> ---
>  kernel/sched/ext/ext.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/sched/ext/ext.c b/kernel/sched/ext/ext.c
> index 691d53fe0f64..cbfa23d71e68 100644
> --- a/kernel/sched/ext/ext.c
> +++ b/kernel/sched/ext/ext.c
> @@ -8572,7 +8572,7 @@ __bpf_kfunc_start_defs();
>   * When called from ops.select_cpu() or ops.enqueue(), it's for direct dispatch
>   * and @p must match the task being enqueued.
>   *
> - * When called from ops.select_cpu(), @enq_flags and @dsp_id are stored, and @p
> + * When called from ops.select_cpu(), @enq_flags and @dsq_id are stored, and @p
>   * will be directly inserted into the corresponding dispatch queue after
>   * ops.select_cpu() returns. If @p is inserted into SCX_DSQ_LOCAL, it will be
>   * inserted into the local DSQ of the CPU returned by ops.select_cpu().
> -- 
> 2.43.0
> 

  reply	other threads:[~2026-07-09 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  8:02 [PATCH] sched_ext: Fix typo in scx_bpf_dsq_insert() comment luoliang
2026-07-09 20:23 ` Andrea Righi [this message]
2026-07-09 21:40 ` 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=alADLIDIRHm3Zwyc@gpd4 \
    --to=arighi@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luoliang@kylinos.cn \
    --cc=sched-ext@lists.linux.dev \
    --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.