linux-kernel - [PATCH] dma-buf: Fix minor typo in struct dma_buf

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

Message-ID: <87k0nvn5ne.fsf@gmail.com>
Date:   Tue, 18 May 2021 23:13:51 +0200
From:   Waqar Hameed <whame91@...il.com>
To:     Sumit Semwal <sumit.semwal@...aro.org>,
        Christian König <christian.koenig@....com>
Cc:     linux-kernel@...r.kernel.org, trivial@...nel.org
Subject: [PATCH] dma-buf: Fix minor typo in struct dma_buf_ops documentation

Just a minor typo.

Signed-off-by: Waqar Hameed <whame91@...il.com>
---
 include/linux/dma-buf.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/dma-buf.h b/include/linux/dma-buf.h
index efdc56b9d95f..5ae51bab158b 100644
--- a/include/linux/dma-buf.h
+++ b/include/linux/dma-buf.h
@@ -50,7 +50,7 @@ struct dma_buf_ops {
 	 * &dma_buf_attachment.dev can access the provided &dma_buf. Exporters
 	 * which support buffer objects in special locations like VRAM or
 	 * device-specific carveout areas should check whether the buffer could
-	 * be move to system memory (or directly accessed by the provided
+	 * be moved to system memory (or directly accessed by the provided
 	 * device), and otherwise need to fail the attach operation.
 	 *
 	 * The exporter should also in general check whether the current
-- 
2.25.1