sched/cpu-timers: task->signal is stable now
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 13 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | sched: __sched_setscheduler: read RLIMIT_RTPRIO locklesskernel/ | +2 | 1 reply | |
| 2/5 | sched: task_tick_rt: remove the obsolete ->signal != NULL checkkernel/ | +0 | 1 reply | |
| 3/5 | sched_stats: remove the obsolete exit_state/signal hackskernel/ | +3 | 1 reply | |
| 4/5 | thread_group_cputime: simplify, document the "alive" checkkernel/ | +7 | 5 replies | |
| 5/5 | run_posix_cpu_timers: don't check ->exit_state, use lock_task_sighand()kernel/ | +4 | 4 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] sched/cpu-timers: task->signal is stable now
With the recent changes task->signal is pinned to task_struct, it is always valid and can't go away. We can simplify some code in sched / posix-cpu-timers files.
Oleg.