summaryrefslogtreecommitdiffstats
path: root/REPORTING-BUGS
diff options
context:
space:
mode:
authorJun'ichi Nomura <j-nomura@ce.jp.nec.com>2006-10-30 16:23:56 -0500
committerLinus Torvalds <torvalds@g5.osdl.org>2006-10-30 19:29:41 -0800
commitdf6c0cd9a872ebf2298f5d66d8c789f62dbe35fc (patch)
treec2d9ecf8ebb71f27aef1b5cc9dd94453e3d18150 /REPORTING-BUGS
parentbcb55165d3d1ae3ec95807d118fd6d5956cd127b (diff)
downloadop-kernel-dev-df6c0cd9a872ebf2298f5d66d8c789f62dbe35fc.zip
op-kernel-dev-df6c0cd9a872ebf2298f5d66d8c789f62dbe35fc.tar.gz
[PATCH] clean up add_bd_holder()
add_bd_holder() is called from bd_claim_by_kobject to put a given struct bd_holder in the list if there is no matching entry. There are 3 possible results of add_bd_holder(): 1. there is no matching entry and add the given one to the list 2. there is matching entry, so just increment reference count of the existing one 3. something failed during its course 1 and 2 are successful cases. But for case 2, someone has to free the unused struct bd_holder. The current code frees it inside of add_bd_holder and returns same value 0 for both cases 1 and 2. However, it's natural and less error-prone if caller frees it since it's allocated by the caller. Signed-off-by: Jun'ichi Nomura <j-nomura@ce.jp.nec.com> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'REPORTING-BUGS')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud