|
On Thu, Nov 3, 2022 at 10:48 PM Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
>
> Ideally, I would have the first patch go into this rc cycle, which is mostly
> non functional as it will allow the other patches to come in via the
> respective
> subsystems in the next merge window.
Ack.
I also wonder if we could do the completely trivially correct
conversions immediately.
I'm talking about the scripted ones where it's currently a
"del_timer_sync()", and the very next action is freeing whatever data
structure the timer is in (possibly with something like free_irq() in
between - my point is that there's an unconditional free that is very
clear and unambiguous), so that there is absolutely no question about
whether they should use "timer_shutdown_sync()" or not.
IOW, things like patches 03, 17 and 31, and at least parts others in
this series.
This series clearly has several much more complex cases that need
actual real code review, and I think it would help to have the
completely unambiguous cases out of the way, just to get rid of noise.
So I'd take that first patch, and a scripted set of "this cannot
change any semantics" patches early.
Linus
|
