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

[Ohad Ben-Cohen]

On Sat, Jun 1, 2013 at 12:16 AM, Suman Anna <s-anna@xxxxxx> 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.
>
> This is mostly a no-op since the remote processors are already
> stopped when the cleanup function is called, but this will make
> the cleanup code follow the exact reverse path of allocation.
>
> Signed-off-by: Suman Anna <s-anna@xxxxxx>

Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/