aboutsummaryrefslogtreecommitdiffstats
path: root/fs/partitions/ultrix.c
diff options
context:
space:
mode:
authorTejun Heo <tj@kernel.org>2010-05-15 20:09:29 +0200
committerJens Axboe <jens.axboe@oracle.com>2010-05-21 20:01:02 +0200
commitc3e33e043f5e9c583aa59d5591a614b2a8243d3a (patch)
treefe8fef91dafb670fad1f433ae48514472b8d23e5 /fs/partitions/ultrix.c
parent56bca01738733709bef076e2e97bbd01e5659f24 (diff)
downloadkernel_samsung_tuna-c3e33e043f5e9c583aa59d5591a614b2a8243d3a.zip
kernel_samsung_tuna-c3e33e043f5e9c583aa59d5591a614b2a8243d3a.tar.gz
kernel_samsung_tuna-c3e33e043f5e9c583aa59d5591a614b2a8243d3a.tar.bz2
block,ide: simplify bdops->set_capacity() to ->unlock_native_capacity()
bdops->set_capacity() is unnecessarily generic. All that's required is a simple one way notification to lower level driver telling it to try to unlock native capacity. There's no reason to pass in target capacity or return the new capacity. The former is always the inherent native capacity and the latter can be handled via the usual device resize / revalidation path. In fact, the current API is always used that way. Replace ->set_capacity() with ->unlock_native_capacity() which take only @disk and doesn't return anything. IDE which is the only current user of the API is converted accordingly. Signed-off-by: Tejun Heo <tj@kernel.org> Cc: Ben Hutchings <ben@decadent.org.uk> Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> Acked-by: David S. Miller <davem@davemloft.net> Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Diffstat (limited to 'fs/partitions/ultrix.c')
0 files changed, 0 insertions, 0 deletions