clockevents: Use list_move() instead of list_del()/list_add()

Simplify the code.

Reported-by: Hulk Robot <hulkci@huawei.com>
Signed-off-by: Baokun Li <libaokun1@huawei.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Link: https://lore.kernel.org/r/20210609070242.1322450-1-libaokun1@huawei.com

diff --git a/kernel/time/clockevents.c b/kernel/time/clockevents.c
index bb9d2fe584804b6fe406012b702832c77797b640..003ccf338d2017c26441d2492be331fbad30d283 100644 (file)
--- a/kernel/time/clockevents.c
+++ b/kernel/time/clockevents.c
@@ -347,8 +347,7 @@ static void clockevents_notify_released(void)
        while (!list_empty(&clockevents_released)) {
                dev = list_entry(clockevents_released.next,
                                 struct clock_event_device, list);
-               list_del(&dev->list);
-               list_add(&dev->list, &clockevent_devices);
+               list_move(&dev->list, &clockevent_devices);
                tick_check_new_device(dev);
        }
 }
@@ -576,8 +575,7 @@ void clockevents_exchange_device(struct clock_event_device *old,
        if (old) {
                module_put(old->owner);
                clockevents_switch_state(old, CLOCK_EVT_STATE_DETACHED);
-               list_del(&old->list);
-               list_add(&old->list, &clockevents_released);
+               list_move(&old->list, &clockevents_released);
        }
 
        if (new) {