Re: [PATCH 3/3] remoteproc: free carveout memories only after unmapping them

2013-07-01 Thread Ohad Ben-Cohen
On Sat, Jun 1, 2013 at 12:16 AM, Suman Anna wrote: > It is not preferable to have the allocated pages for carveout > memories freed before they are unmapped. The code that deals > with the cleanup of carveout memories is therefore moved after > the corresponding mapping entries were cleaned up. >

Re: [PATCH 3/3] remoteproc: free carveout memories only after unmapping them

2013-07-01 Thread Ohad Ben-Cohen
On Sat, Jun 1, 2013 at 12:16 AM, Suman Anna s-a...@ti.com wrote: It is not preferable to have the allocated pages for carveout memories freed before they are unmapped. The code that deals with the cleanup of carveout memories is therefore moved after the corresponding mapping entries were

[PATCH 3/3] remoteproc: free carveout memories only after unmapping them

2013-05-31 Thread Suman Anna
It is not preferable to have the allocated pages for carveout memories freed before they are unmapped. The code that deals with the cleanup of carveout memories is therefore moved after the corresponding mapping entries were cleaned up. This is mostly a no-op since the remote processors are

[PATCH 3/3] remoteproc: free carveout memories only after unmapping them

2013-05-31 Thread Suman Anna
It is not preferable to have the allocated pages for carveout memories freed before they are unmapped. The code that deals with the cleanup of carveout memories is therefore moved after the corresponding mapping entries were cleaned up. This is mostly a no-op since the remote processors are