diff options
| author | Randy Dunlap <rdunlap@infradead.org> | 2023-01-30 00:10:46 +0100 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2023-02-02 19:05:16 +0100 |
| commit | 7852fe3a092721794f92c4d04fb33184501a3c9a (patch) | |
| tree | 93a74dd046406e3e177d5d43cf45229835208042 /Documentation/driver-api/dmaengine/client.rst | |
| parent | Documentation: admin-guide: correct spelling (diff) | |
| download | linux-7852fe3a092721794f92c4d04fb33184501a3c9a.tar.xz linux-7852fe3a092721794f92c4d04fb33184501a3c9a.zip | |
Documentation: driver-api: correct spelling
Correct spelling problems for Documentation/driver-api/ as reported
by codespell.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org
Cc: Vishal Verma <vishal.l.verma@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>
Cc: nvdimm@lists.linux.dev
Cc: Vinod Koul <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org
Cc: linux-raid@vger.kernel.org
Cc: linux-usb@vger.kernel.org
Acked-by: Dan Williams <dan.j.williams@intel.com>
Acked-by: Song Liu <song@kernel.org>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Link: https://lore.kernel.org/r/20230129231053.20863-3-rdunlap@infradead.org
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/driver-api/dmaengine/client.rst')
| -rw-r--r-- | Documentation/driver-api/dmaengine/client.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/driver-api/dmaengine/client.rst b/Documentation/driver-api/dmaengine/client.rst index bfd057b21a00..ecf139f73da4 100644 --- a/Documentation/driver-api/dmaengine/client.rst +++ b/Documentation/driver-api/dmaengine/client.rst @@ -175,7 +175,7 @@ The details of these operations are: driver can ask for the pointer, maximum size and the currently used size of the metadata and can directly update or read it. - Becasue the DMA driver manages the memory area containing the metadata, + Because the DMA driver manages the memory area containing the metadata, clients must make sure that they do not try to access or get the pointer after their transfer completion callback has run for the descriptor. If no completion callback has been defined for the transfer, then the |