Hello,
On 3/19/2013 3:24 PM, Luis Henriques wrote:
Hi Marek,
On Tue, Mar 19, 2013 at 08:24:21AM +0100, Marek Szyprowski wrote:
> commit 9d1400cf79afb49584b4873eb22cd5130cb341db upstream.
>
> Atomic pool should always be allocated from DMA zone if such zone is
> available in the system to avoid issues caused by limited dma mask of
> any of the devices used for making an atomic allocation.
>
> Reported-by: Krzysztof Halasa <k...@pm.waw.pl>
> Signed-off-by: Marek Szyprowski <m.szyprow...@samsung.com>
> Cc: Stable <stable@vger.kernel.org> [v3.6+]
> ---
> Hello,
>
> This is a backported version of mainline 9d1400cf79afb49584b commit.
> It should apply fine to v3.8.y, v3.7.y and v3.6.y stable kernel trees.
Could you confirm this should *not* be added to 3.5 kernels?
This patch fixes issue introduced by commit
e9da6e9905e639b0f842a244bc770b48ad0523e9,
which has been merged to v3.6-rc1. All v3.5.x and earlier are not
affected by this
bug. I should have added such information to commit message to avoid
confusion.
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html