[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080330232836.GX28445@cs181133002.pp.htv.fi>
Date: Mon, 31 Mar 2008 02:28:36 +0300
From: Adrian Bunk <bunk@...nel.org>
To: dm-devel@...hat.com
Cc: linux-kernel@...r.kernel.org
Subject: [2.6 patch] make dm_set_device_limits() static
This patch makes the needlessly global dm_set_device_limits() static.
Signed-off-by: Adrian Bunk <bunk@...nel.org>
---
drivers/md/dm-table.c | 4 ++--
include/linux/device-mapper.h | 5 -----
2 files changed, 2 insertions(+), 7 deletions(-)
bb081f9ddde6ca766b8c1cd1077f203d0a082cdb diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c
index a999211..ce27283 100644
--- a/drivers/md/dm-table.c
+++ b/drivers/md/dm-table.c
@@ -491,7 +491,8 @@ static int __table_get_device(struct dm_table *t, struct dm_target *ti,
return 0;
}
-void dm_set_device_limits(struct dm_target *ti, struct block_device *bdev)
+static void dm_set_device_limits(struct dm_target *ti,
+ struct block_device *bdev)
{
struct request_queue *q = bdev_get_queue(bdev);
struct io_restrictions *rs = &ti->limits;
@@ -541,7 +542,6 @@ void dm_set_device_limits(struct dm_target *ti, struct block_device *bdev)
rs->no_cluster |= !test_bit(QUEUE_FLAG_CLUSTER, &q->queue_flags);
}
-EXPORT_SYMBOL_GPL(dm_set_device_limits);
int dm_get_device(struct dm_target *ti, const char *path, sector_t start,
sector_t len, int mode, struct dm_dev **result)
diff --git a/include/linux/device-mapper.h b/include/linux/device-mapper.h
index 8fc199b..4c4b3a6 100644
--- a/include/linux/device-mapper.h
+++ b/include/linux/device-mapper.h
@@ -75,11 +75,6 @@ typedef int (*dm_ioctl_fn) (struct dm_target *ti, struct inode *inode,
void dm_error(const char *message);
/*
- * Combine device limits.
- */
-void dm_set_device_limits(struct dm_target *ti, struct block_device *bdev);
-
-/*
* Constructors should call these functions to ensure destination devices
* are opened/closed correctly.
* FIXME: too many arguments.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists