summaryrefslogtreecommitdiff
path: root/drivers/md/dm-table.c
diff options
context:
space:
mode:
authorJens Axboe <jens.axboe@oracle.com>2009-06-09 08:22:57 +0400
committerJens Axboe <jens.axboe@oracle.com>2009-06-09 08:22:57 +0400
commit9df1bb9b516daeece159ab7fb262d01a0359247c (patch)
tree602c7b02e85b031d0269a1f70ece81bac524c0ac /drivers/md/dm-table.c
parent3969251b80a7b143d01576780073fe0cc9ef6253 (diff)
downloadlinux-9df1bb9b516daeece159ab7fb262d01a0359247c.tar.xz
Revert "block: Fix bounce limit setting in DM"
This reverts commit a05c0205ba031c01bba33a21bf0a35920eb64833. DM doesn't need to access the bounce_pfn directly. Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Diffstat (limited to 'drivers/md/dm-table.c')
-rw-r--r--drivers/md/dm-table.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c
index 3ca1604ddd5c..e9a73bb242b0 100644
--- a/drivers/md/dm-table.c
+++ b/drivers/md/dm-table.c
@@ -920,7 +920,7 @@ void dm_table_set_restrictions(struct dm_table *t, struct request_queue *q)
blk_queue_max_segment_size(q, t->limits.max_segment_size);
blk_queue_max_hw_sectors(q, t->limits.max_hw_sectors);
blk_queue_segment_boundary(q, t->limits.seg_boundary_mask);
- blk_queue_bounce_pfn(q, t->limits.bounce_pfn);
+ blk_queue_bounce_limit(q, t->limits.bounce_pfn);
if (t->limits.no_cluster)
queue_flag_clear_unlocked(QUEUE_FLAG_CLUSTER, q);