linux-kernel - [PATCH -next] goldfish: use list_move_tail instead of list_del/list_add

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAPgLHd9DUb+o9YQADJYhgWoxX0767PnEBkZf_OT6R1WtNhAOKw@mail.gmail.com>
Date:	Mon, 11 Mar 2013 23:38:38 +0800
From:	Wei Yongjun <weiyj.lk@...il.com>
To:	yunhong.jiang@...el.com, sheng@...ux.intel.com,
	bruce.j.beare@...el.com, gregkh@...uxfoundation.org,
	xiaohui.xin@...el.com
Cc:	yongjun_wei@...ndmicro.com.cn, linux-kernel@...r.kernel.org
Subject: [PATCH -next] goldfish: use list_move_tail instead of list_del/list_add_tail

From: Wei Yongjun <yongjun_wei@...ndmicro.com.cn>

Using list_move_tail() instead of list_del() + list_add_tail().

Signed-off-by: Wei Yongjun <yongjun_wei@...ndmicro.com.cn>
---
 drivers/platform/goldfish/pdev_bus.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/platform/goldfish/pdev_bus.c b/drivers/platform/goldfish/pdev_bus.c
index 92cc4cf..816faf0 100644
--- a/drivers/platform/goldfish/pdev_bus.c
+++ b/drivers/platform/goldfish/pdev_bus.c
@@ -91,8 +91,7 @@ static void goldfish_pdev_remove(void)
 	}
 	list_for_each_entry_safe(pos, n, &pdev_bus_registered_devices, list) {
 		if (pos->resources[0].start == base) {
-			list_del(&pos->list);
-			list_add_tail(&pos->list, &pdev_bus_removed_devices);
+			list_move_tail(&pos->list, &pdev_bus_removed_devices);
 			schedule_work(&pdev_bus_worker);
 			return;
 		}

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/