[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1VMnpO-0001Kt-E7@rmk-PC.arm.linux.org.uk>
Date: Fri, 20 Sep 2013 00:40:06 +0100
From: Russell King <rmk+kernel@....linux.org.uk>
To: alsa-devel@...a-project.org, b43-dev@...ts.infradead.org,
devel@...verdev.osuosl.org, devicetree@...r.kernel.org,
dri-devel@...ts.freedesktop.org, e1000-devel@...ts.sourceforge.net,
linux-arm-kernel@...ts.infradead.org, linux-crypto@...r.kernel.org,
linux-doc@...r.kernel.org, linux-fbdev@...r.kernel.org,
linux-ide@...r.kernel.org, linux-media@...r.kernel.org,
linux-mmc@...r.kernel.org, linux-nvme@...ts.infradead.org,
linux-omap@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
linux-samsung-soc@...r.kernel.org, linux-scsi@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-usb@...r.kernel.org,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
Solarflare linux maintainers <linux-net-drivers@...arflare.com>,
uclinux-dist-devel@...ckfin.uclinux.org
Cc: Jens Axboe <axboe@...nel.dk>, Jens Axboe <axboe@...nel.dk>
Subject: [PATCH 47/51] ARM: 7794/1: block: Rename parameter dma_mask to
max_addr for blk_queue_bounce_limit()
From: Santosh Shilimkar <santosh.shilimkar@...com>
The blk_queue_bounce_limit() API parameter 'dma_mask' is actually the
maximum address the device can handle rather than a dma_mask. Rename
it accordingly to avoid it being interpreted as dma_mask.
No functional change.
The idea is to fix the bad assumptions about dma_mask wherever it could
be miss-interpreted.
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@...com>
Signed-off-by: Russell King <rmk+kernel@....linux.org.uk>
---
block/blk-settings.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/block/blk-settings.c b/block/blk-settings.c
index c50ecf0..026c151 100644
--- a/block/blk-settings.c
+++ b/block/blk-settings.c
@@ -195,17 +195,17 @@ EXPORT_SYMBOL(blk_queue_make_request);
/**
* blk_queue_bounce_limit - set bounce buffer limit for queue
* @q: the request queue for the device
- * @dma_mask: the maximum address the device can handle
+ * @max_addr: the maximum address the device can handle
*
* Description:
* Different hardware can have different requirements as to what pages
* it can do I/O directly to. A low level driver can call
* blk_queue_bounce_limit to have lower memory pages allocated as bounce
- * buffers for doing I/O to pages residing above @dma_mask.
+ * buffers for doing I/O to pages residing above @max_addr.
**/
-void blk_queue_bounce_limit(struct request_queue *q, u64 dma_mask)
+void blk_queue_bounce_limit(struct request_queue *q, u64 max_addr)
{
- unsigned long b_pfn = dma_mask >> PAGE_SHIFT;
+ unsigned long b_pfn = max_addr >> PAGE_SHIFT;
int dma = 0;
q->bounce_gfp = GFP_NOIO;
--
1.7.4.4
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists