The patch titled
     usb: dma bounce buffer support V3 (fix)
has been removed from the -mm tree.  Its filename was
     usb-dma-bounce-buffer-support-v3-fix.patch

This patch was dropped because it was merged into mainline or a subsystem tree

The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/

------------------------------------------------------
Subject: usb: dma bounce buffer support V3 (fix)
From: "Magnus Damm" <[EMAIL PROTECTED]>

Cc: Alan Stern <[EMAIL PROTECTED]>
Cc: Greg KH <[EMAIL PROTECTED]>
Cc: David Brownell <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 drivers/usb/core/hcd.c |    8 ++++++++
 1 file changed, 8 insertions(+)

diff -puN drivers/usb/core/hcd.c~usb-dma-bounce-buffer-support-v3-fix 
drivers/usb/core/hcd.c
--- a/drivers/usb/core/hcd.c~usb-dma-bounce-buffer-support-v3-fix
+++ a/drivers/usb/core/hcd.c
@@ -1125,6 +1125,14 @@ static int hcd_alloc_coherent(struct usb
        if (!vaddr)
                return -ENOMEM;
 
+       /*
+        * Store the virtual address of the buffer at the end
+        * of the allocated dma buffer. The size of the buffer
+        * may be uneven so use unaligned functions instead
+        * of just rounding up. It makes sense to optimize for
+        * memory footprint over access speed since the amount
+        * of memory available for dma may be limited.
+        */
        put_unaligned((unsigned long)*vaddr_handle,
                      (unsigned long *)(vaddr + size));
 
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

git-sh.patch
usb-ohci-sm501-driver-v2-fix.patch
spi-superh-spi-using-sci.patch
rtc-add-support-for-epson-rtc-9701je-v2.patch
rtc-add-support-for-epson-rtc-9701je-v4.patch
sm501fb-control-panel-pin-usage-with-platform-data-flags.patch
sm501fb-clear-framebuffer-memory-and-palette.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to