From: Deng-Cheng Zhu <dengcheng.zhu@gmail.com>
To: jbarnes@virtuousgeek.org, torvalds@linux-foundation.org
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@linux-mips.org, eyal@mips.com, zenon@mips.com,
dengcheng.zhu@gmail.com
Subject: [PATCH 2/2] kernel/resource: enrich the comment for insert_resource_conflict()
Date: Thu, 28 Jul 2011 19:28:32 +0800 [thread overview]
Message-ID: <1311852512-7340-3-git-send-email-dengcheng.zhu@gmail.com> (raw)
In-Reply-To: <1311852512-7340-1-git-send-email-dengcheng.zhu@gmail.com>
It helps people better understand how this function works.
Signed-off-by: Deng-Cheng Zhu <dengcheng.zhu@gmail.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
prev parent reply other threads:[~2011-07-28 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 11:28 [PATCH 0/2] PCI driver to use insert_resource_conflict() to claim resources Deng-Cheng Zhu
2011-07-28 11:28 ` [PATCH 1/2] PCI: make pci_claim_resource() work with conflict resources as appropriate Deng-Cheng Zhu
2011-07-28 11:53 ` Ralf Baechle
2011-07-29 6:32 ` Deng-Cheng Zhu
2011-07-29 17:35 ` Bjorn Helgaas
2011-08-01 10:13 ` Deng-Cheng Zhu
2011-08-01 15:21 ` Bjorn Helgaas
2011-07-28 15:59 ` Bjorn Helgaas
2011-07-29 6:35 ` Deng-Cheng Zhu
2011-07-28 11:28 ` Deng-Cheng Zhu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1311852512-7340-3-git-send-email-dengcheng.zhu@gmail.com \
--to=dengcheng.zhu@gmail.com \
--cc=eyal@mips.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-pci@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zenon@mips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®