linux-kernel - Re: [PATCH 2/2] dma-mapping: remove dma_max

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <2cf24650-512e-688d-fe24-119d36ed92f5@free.fr>
Date:   Tue, 25 Jun 2019 13:45:38 +0200
From:   Marc Gonzalez <marc.w.gonzalez@...e.fr>
To:     Christoph Hellwig <hch@....de>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [PATCH 2/2] dma-mapping: remove dma_max_pfn

Hello Christoph,

There are some typos in the commit message that make it harder
(for me) to parse.

On 25/06/2019 11:20, Christoph Hellwig wrote:

> These days the DMA mapping code must bounce buffer for any not supported

Add comma after "These days" ?
s/must bounce buffer/must bounce buffers/ ?
s/not supported/unsupported/ ?

> address, and if they driver needs to optimize for natively supported

s/if they driver/if the driver/ ?

> ranged it should use dma_get_required_mask.

s/ranged it should/ranges, then it should/ ?

Regards.