Re: [PATCH v2 1/4] sched: Rename/clarify sched_class::task_tick(.queued) argument

[Kayra Cizmeci]

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@xxxxxxxxx>
> > 
> > (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@xxxxxxxxxxxxxxx
> 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!