Re: [PATCH] Staging: TIDSPBRIDGE: Use vm_iomap_memory for mmap-ing instead of remap_pfn_range

2013-12-11 Thread Dan Carpenter
On Wed, Dec 11, 2013 at 09:45:52AM +0200, Ivajlo Dimitrov wrote: I can pick your changes and re-send the original patch with them incorporated if there are no objections. Are you fine with that? Do it on top of staging-next, don't redo the original. regards, dan carpenter

Re: [PATCH] Staging: TIDSPBRIDGE: Use vm_iomap_memory for mmap-ing instead of remap_pfn_range

2013-12-11 Thread Ivaylo Dimitrov
On 11.12.2013 10:33, Dan Carpenter wrote: On Wed, Dec 11, 2013 at 09:45:52AM +0200, Ivajlo Dimitrov wrote: I can pick your changes and re-send the original patch with them incorporated if there are no objections. Are you fine with that? Do it on top of staging-next, don't redo the original.

Re: [PATCH] Staging: TIDSPBRIDGE: Use vm_iomap_memory for mmap-ing instead of remap_pfn_range

2013-12-11 Thread Dan Carpenter
On Wed, Dec 11, 2013 at 11:57:04AM +0200, Ivaylo Dimitrov wrote: On 11.12.2013 10:33, Dan Carpenter wrote: On Wed, Dec 11, 2013 at 09:45:52AM +0200, Ivajlo Dimitrov wrote: I can pick your changes and re-send the original patch with them incorporated if there are no objections. Are you fine

Re: [PATCH] Staging: TIDSPBRIDGE: Use vm_iomap_memory for mmap-ing instead of remap_pfn_range

2013-12-11 Thread Greg KH
On Wed, Dec 11, 2013 at 01:27:17PM +0300, Dan Carpenter wrote: On Wed, Dec 11, 2013 at 11:57:04AM +0200, Ivaylo Dimitrov wrote: On 11.12.2013 10:33, Dan Carpenter wrote: On Wed, Dec 11, 2013 at 09:45:52AM +0200, Ivajlo Dimitrov wrote: I can pick your changes and re-send the original patch

Re: [PATCH] Staging: TIDSPBRIDGE: Use vm_iomap_memory for mmap-ing instead of remap_pfn_range

2013-12-10 Thread Ivajlo Dimitrov
On 08.12.2013 01:49, Steven Luo wrote: This patch causes problems with DSP codecs on OMAP3 devices running Android -- specifically, when the decoder is cleaning up after itself, munmap() of the mapped area fails, leading to a memory leak which eventually crashes the system. As far as I can

[PATCH] Staging: TIDSPBRIDGE: Use vm_iomap_memory for mmap-ing instead of remap_pfn_range

2013-12-02 Thread Ivaylo DImitrov
From: Ivaylo Dimitrov freemangor...@abv.bg This fixes the following bug: Bug Report source file: drivers/staging/tidspbridge/rmgr/drv_interface.c issue : mapping of physical memory without address range checks 259 static int bridge_mmap(struct file *filp, struct vm_area_struct