| commit | 920b1f427123b7bfcdad472e21c2b259754987b9 | |
| author | Matthew Wilcox <willy@parisc-linux.org> | |
| Thu, 17 Sep 2009 21:00:23 +0000 (17 23:00 +0200) | ||
| committer | james toy <toyj@union.edu> | |
| Thu, 17 Sep 2009 21:00:23 +0000 (17 23:00 +0200) | ||
| tree | fd1f3e09c23b4375dd6e7a23b5dd074ebb427d84 | treesnapshot (tar.gz zip) |
| parent | df396dc5ac5d08d1f0de3a4dd464d9a6df52ffd6 | commitdiff |
What does it mean to release a resource with children? Should the children
become children of the released resource's parent? Should they be released
too? Should we fail the release?
I bet we have no callers who expect this right now, but with
insert_resource() we may get some. At the point where someone hits this
BUG we can figure out what semantics we want.
Signed-off-by: Matthew Wilcox <willy@parisc-linux.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
become children of the released resource's parent? Should they be released
too? Should we fail the release?
I bet we have no callers who expect this right now, but with
insert_resource() we may get some. At the point where someone hits this
BUG we can figure out what semantics we want.
Signed-off-by: Matthew Wilcox <willy@parisc-linux.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
| kernel/resource.c | diffblobblamehistory |