linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] docs/core-api: swiotlb: fix typos
@ 2024-10-14 22:40 Eder Zulian
  2024-10-17 15:38 ` Jonathan Corbet
  0 siblings, 1 reply; 2+ messages in thread
From: Eder Zulian @ 2024-10-14 22:40 UTC (permalink / raw)
  To: corbet; +Cc: linux-doc, linux-kernel

Correct references to swiotlb_tbl_map_single() and
swiotlb_tbl_unmap_single() in the documentation for swiotlb.

Fix two small typos that went unnoticed in commit c93f261dfc39
("Documentation/core-api: add swiotlb documentation"):
swiotlb_tlb_map_single --> swiotlb_tbl_map_single
swiotbl_tlb_unmap_single --> swiotlb_tbl_unmap_single

Signed-off-by: Eder Zulian <ezulian@redhat.com>
---
 Documentation/core-api/swiotlb.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/core-api/swiotlb.rst b/Documentation/core-api/swiotlb.rst
index cf06bae44ff8..9e0fe027dd3b 100644
--- a/Documentation/core-api/swiotlb.rst
+++ b/Documentation/core-api/swiotlb.rst
@@ -295,9 +295,9 @@ slot set.
 
 Fourth, the io_tlb_slot array keeps track of any "padding slots" allocated to
 meet alloc_align_mask requirements described above. When
-swiotlb_tlb_map_single() allocates bounce buffer space to meet alloc_align_mask
+swiotlb_tbl_map_single() allocates bounce buffer space to meet alloc_align_mask
 requirements, it may allocate pre-padding space across zero or more slots. But
-when swiotbl_tlb_unmap_single() is called with the bounce buffer address, the
+when swiotlb_tbl_unmap_single() is called with the bounce buffer address, the
 alloc_align_mask value that governed the allocation, and therefore the
 allocation of any padding slots, is not known. The "pad_slots" field records
 the number of padding slots so that swiotlb_tbl_unmap_single() can free them.
-- 
2.46.2


^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH] docs/core-api: swiotlb: fix typos
  2024-10-14 22:40 [PATCH] docs/core-api: swiotlb: fix typos Eder Zulian
@ 2024-10-17 15:38 ` Jonathan Corbet
  0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Corbet @ 2024-10-17 15:38 UTC (permalink / raw)
  To: Eder Zulian; +Cc: linux-doc, linux-kernel

Eder Zulian <ezulian@redhat.com> writes:

> Correct references to swiotlb_tbl_map_single() and
> swiotlb_tbl_unmap_single() in the documentation for swiotlb.
>
> Fix two small typos that went unnoticed in commit c93f261dfc39
> ("Documentation/core-api: add swiotlb documentation"):
> swiotlb_tlb_map_single --> swiotlb_tbl_map_single
> swiotbl_tlb_unmap_single --> swiotlb_tbl_unmap_single
>
> Signed-off-by: Eder Zulian <ezulian@redhat.com>
> ---
>  Documentation/core-api/swiotlb.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/core-api/swiotlb.rst b/Documentation/core-api/swiotlb.rst
> index cf06bae44ff8..9e0fe027dd3b 100644
> --- a/Documentation/core-api/swiotlb.rst
> +++ b/Documentation/core-api/swiotlb.rst
> @@ -295,9 +295,9 @@ slot set.
>  
>  Fourth, the io_tlb_slot array keeps track of any "padding slots" allocated to
>  meet alloc_align_mask requirements described above. When
> -swiotlb_tlb_map_single() allocates bounce buffer space to meet alloc_align_mask
> +swiotlb_tbl_map_single() allocates bounce buffer space to meet alloc_align_mask
>  requirements, it may allocate pre-padding space across zero or more slots. But
> -when swiotbl_tlb_unmap_single() is called with the bounce buffer address, the
> +when swiotlb_tbl_unmap_single() is called with the bounce buffer address, the

Wow ... that seems like the kind of function naming that is just
designed to cause errors of this type.  Applied, thanks.

jon

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2024-10-17 15:38 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-10-14 22:40 [PATCH] docs/core-api: swiotlb: fix typos Eder Zulian
2024-10-17 15:38 ` Jonathan Corbet

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).