From: Kayra Cizmeci <kayracizmeci@gmail.com>
To: Christian Loehle <christian.loehle@arm.com>
Cc: peterz@infradead.org, bsegall@google.com,
dietmar.eggemann@arm.com, juri.lelli@redhat.com,
kprateek.nayak@amd.com, linux-kernel@vger.kernel.org,
mgorman@suse.de, mingo@kernel.org, rostedt@goodmis.org,
tj@kernel.org, vincent.guittot@linaro.org, vschneid@redhat.com
Subject: Re: [PATCH v2 1/4] sched: Rename/clarify sched_class::task_tick(.queued) argument
Date: Fri, 16 Oct 2026 08:32:52 +0300 [thread overview]
Message-ID: <atGzh4IJjRnWEif5@scheduler.schedules> (raw)
In-Reply-To: <5f98f865-6bae-494b-b08f-662e3325370c@arm.com>
On Thu, Oct 15, 2026 at 09:01:15PM +0100, Christian Loehle wrote:
> On 10/13/26 18:14, Kayra Cizmeci wrote:
> >> For some reason the sched_class::task_tick() argument that indicates it being
> >> an hrtick, is called @queued. I'm sure naming is hard and all, but lets fix
> >> this.
> >
> > "For some reason"...
> >
> > I grepped. I think task_tick_stop() is skipped. That's a nit.
> > Just sayingggggg........
> >
> > Aside from that, or with that IDC.
> >
> > Reviewed-by: Kayra Cizmeci <kayracizmeci@gmail.com>
> >
> > (How y'all find things to review? I just go to the threads that I see the messages of. I think
> > That's why I'm a bit late :<)
> >
> >
>
> Depends what kind of patches you're interested in, most kernel developers
> have an elaborate mail filter setup based on linux-kernel@vger.kernel.org
> If it's just scheduler patches, you can either start filtering for "sched:"
> https://lore.kernel.org/lkml/?q=s%3Asched%3A
I set it up yesterday. It works fine, compared
to the old way of typing my message to a .txt and then
sending it with a git send-email command.
>
> or check one of the people in MAINTAINERS (preferably somebody who isn't listed
> for a bunch of other stuff) e.g.:
> https://lore.kernel.org/lkml/?q=t%3Aeggemann+OR+c%3Aeggemann
I'm already tracking down half of sched at this point :-)
Thanks for da tips!
next prev parent reply other threads:[~2026-10-16 5:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 8:49 [PATCH v2 0/4] sched/fair: Rework task_h_load() Peter Zijlstra
2026-09-29 8:49 ` [PATCH v2 1/4] sched: Rename/clarify sched_class::task_tick(.queued) argument Peter Zijlstra
2026-10-13 16:52 ` Vincent Guittot
2026-10-13 17:14 ` Kayra Cizmeci
2026-10-15 20:01 ` Christian Loehle
2026-10-16 5:32 ` Kayra Cizmeci [this message]
2026-11-09 8:44 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2026-11-09 9:28 ` [tip: sched/core] sched/core: " tip-bot2 for Peter Zijlstra
2026-09-29 8:49 ` [PATCH v2 2/4] sched/fair: Fold cfs_rq_of(se) into for_each_sched_entity() Peter Zijlstra
2026-10-13 16:53 ` Vincent Guittot
2026-11-09 8:44 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2026-11-09 9:28 ` tip-bot2 for Peter Zijlstra
2026-09-29 8:49 ` [PATCH v2 3/4] sched/fair: Extend for_each_sched_entity() with a back-link Peter Zijlstra
2026-10-13 16:54 ` Vincent Guittot
2026-10-21 15:52 ` Peter Zijlstra
2026-10-21 16:39 ` Vincent Guittot
2026-11-09 8:44 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2026-11-09 9:28 ` tip-bot2 for Peter Zijlstra
2026-09-29 8:49 ` [PATCH v2 4/4] sched/fair: Rework/fix task_h_load() Peter Zijlstra
2026-09-29 17:46 ` Kayra Cizmeci
2026-09-30 1:16 ` K Prateek Nayak
2026-09-30 5:45 ` Kayra Cizmeci
2026-09-30 8:45 ` Peter Zijlstra
2026-09-30 10:20 ` Kayra Cizmeci
2026-09-30 11:25 ` Peter Zijlstra
2026-09-30 11:44 ` Kayra Cizmeci
2026-10-01 21:16 ` Kayra Cizmeci
2026-10-13 16:56 ` Vincent Guittot
2026-11-09 8:44 ` [tip: sched/core] " tip-bot2 for Peter Zijlstra
2026-11-09 9:28 ` tip-bot2 for Peter Zijlstra
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=atGzh4IJjRnWEif5@scheduler.schedules \
--to=kayracizmeci@gmail.com \
--cc=bsegall@google.com \
--cc=christian.loehle@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.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 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.