linux-kernel - Re: [RFC PATCH v3 0/2] Expose DMA_MEMORY

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-id: <5645E978.9030603@samsung.com>
Date:	Fri, 13 Nov 2015 14:45:28 +0100
From:	Marek Szyprowski <m.szyprowski@...sung.com>
To:	Neil Armstrong <narmstrong@...libre.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
	Grant Likely <grant.likely@...aro.org>,
	Rob Herring <robh+dt@...nel.org>
Subject: Re: [RFC PATCH v3 0/2] Expose DMA_MEMORY_EXCLUSIVE through
 shared-dma-pool

Hello,

On 2015-11-10 17:18, Neil Armstrong wrote:
> The shared-dma-pool dt node only exposes exclusive memory, but in order to export
> non-exclusive coherent memory, add the no-exclusive property and document it.
>
> v3: use correct of_get_flat_dt_prop helper
> v2: simplify patch by looking for DT attribute in callback
>
> Neil Armstrong (2):
>    base: dma-coherent: Add DT property for non exclusive shared-dma-pool
>    devicetree: reserved-memory: document the optional no-exclusive parameter
>
>   .../devicetree/bindings/reserved-memory/reserved-memory.txt         | 3 +++
>   drivers/base/dma-coherent.c                                         | 6 +++++-
>   2 files changed, 8 insertions(+), 1 deletion(-)
>

Acked-by: Marek Szyprowski <m.szyprowski@...sung.com>

Best regards
-- 
Marek Szyprowski, PhD
Samsung R&D Institute Poland

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