On 05/15/24 08:50, Phil Auld wrote:
> > > My point was just to call it rt_task() still.
> >
> > It is called rt_task() still. I just added a new realtime_task() to return true
> > for RT and DL. rt_task() will return true only for RT now.
> >
> > How do you see this should be done instead? I'm not seeing the problem.
> >
>
> Right, sorry. I misread your commit message completely and then all the
> places where you changed rt_task() to realtime_task() fit my misreading.
>
> rt_task() means rt class and realtime_task does what rt_task() used to do.
> That's how I would do it, too :)
Ah, I see. I updated the commit message to hopefully read better :)
"""
I define the usage of rt_task() to be tasks that belong to RT class.
Make sure that it returns true only for RT class and audit the users and
replace the ones required the old behavior with the new realtime_task()
which returns true for RT and DL classes. Introduce similar
realtime_prio() to create similar distinction to rt_prio() and update
the users that required the old behavior to use the new function.
"""
> Reviewed-by: Phil Auld <pauld@xxxxxxxxxx>
Thanks for having a look!
Cheers
--
Qais Yousef
