[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1311852512-7340-3-git-send-email-dengcheng.zhu@gmail.com>
Date: Thu, 28 Jul 2011 19:28:32 +0800
From: Deng-Cheng Zhu <dengcheng.zhu@...il.com>
To: jbarnes@...tuousgeek.org, torvalds@...ux-foundation.org
Cc: linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mips@...ux-mips.org, eyal@...s.com, zenon@...s.com,
dengcheng.zhu@...il.com
Subject: [PATCH 2/2] kernel/resource: enrich the comment for insert_resource_conflict()
It helps people better understand how this function works.
Signed-off-by: Deng-Cheng Zhu <dengcheng.zhu@...il.com>
---
kernel/resource.c | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/kernel/resource.c b/kernel/resource.c
index 3ff4017..5406ecf 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -617,7 +617,9 @@ static struct resource * __insert_resource(struct resource *parent, struct resou
* happens. If a conflict happens, and the conflicting resources
* entirely fit within the range of the new resource, then the new
* resource is inserted and the conflicting resources become children of
- * the new resource.
+ * the new resource. Also, if the new resource entirely fits within the range
+ * of a conflicting resource without overlapping the latter's children, then
+ * the new resource is inserted too and becomes a child of the conflicting one.
*/
struct resource *insert_resource_conflict(struct resource *parent, struct resource *new)
{
--
1.7.1
--
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/
Powered by blists - more mailing lists