public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yajun Deng <yajun.deng@linux.dev>
To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
	rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
	bristot@redhat.com, vschneid@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] sched: Return NULL when entity isn't a task
Date: Tue, 23 Jan 2024 11:19:35 +0800	[thread overview]
Message-ID: <9c474667-e1b3-18fa-e7dd-a9c1228091df@linux.dev> (raw)
In-Reply-To: <20231206063400.3206346-1-yajun.deng@linux.dev>

Kindly ping...

Thanks


On 2023/12/6 14:33, Yajun Deng wrote:
> If the entity isn't a task, return the task struct is meaningless.
> Return NULL when entity isn't a task that makes the code more concise.
>
> v1 -> v2:
> fix 'struct rt_rq' no member named 'highest_prio'.
>
> Yajun Deng (2):
>    sched/fair: Return NULL when entity isn't a task in task_of()
>    sched/rt: Return NULL when rt entity isn't a task in rt_task_of()
>
>   kernel/sched/fair.c  | 50 ++++++++++++++++++------------------
>   kernel/sched/rt.c    | 60 +++++++++++++-------------------------------
>   kernel/sched/sched.h |  4 ++-
>   3 files changed, 44 insertions(+), 70 deletions(-)
>

      parent reply	other threads:[~2024-01-23  3:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06  6:33 [PATCH v2 0/2] sched: Return NULL when entity isn't a task Yajun Deng
2023-12-06  6:33 ` [PATCH v2 1/2] sched/fair: Return NULL when entity isn't a task in task_of() Yajun Deng
2024-01-23  3:48   ` Steven Rostedt
2024-01-24  8:08     ` Yajun Deng
2023-12-06  6:34 ` [PATCH v2 2/2] sched/rt: Return NULL when rt entity isn't a task in rt_task_of() Yajun Deng
2024-01-23  3:19 ` Yajun Deng [this message]

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=9c474667-e1b3-18fa-e7dd-a9c1228091df@linux.dev \
    --to=yajun.deng@linux.dev \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox