aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChris Packham <chris.packham@alliedtelesis.co.nz>2019-10-25 08:50:14 +1300
committerJonathan Corbet <corbet@lwn.net>2019-10-29 04:44:48 -0600
commitef8330fe02710046d7b6ce271d821926dd2769e8 (patch)
tree91148531c835986e5beff3810cdd0ccd12a4ec22
parentMerge tag 'v5.4-rc4' into docs-next (diff)
downloadlinux-dev-ef8330fe02710046d7b6ce271d821926dd2769e8.tar.xz
linux-dev-ef8330fe02710046d7b6ce271d821926dd2769e8.zip
docs/core-api: memory-allocation: fix typo
"on the safe size" should be "on the safe side". Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz> Acked-by: Mike Rapoport <rppt@linux.ibm.com> Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
-rw-r--r--Documentation/core-api/memory-allocation.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/core-api/memory-allocation.rst b/Documentation/core-api/memory-allocation.rst
index 939e3dfc86e9..dcf851b4520f 100644
--- a/Documentation/core-api/memory-allocation.rst
+++ b/Documentation/core-api/memory-allocation.rst
@@ -88,7 +88,7 @@ Selecting memory allocator
==========================
The most straightforward way to allocate memory is to use a function
-from the :c:func:`kmalloc` family. And, to be on the safe size it's
+from the :c:func:`kmalloc` family. And, to be on the safe side it's
best to use routines that set memory to zero, like
:c:func:`kzalloc`. If you need to allocate memory for an array, there
are :c:func:`kmalloc_array` and :c:func:`kcalloc` helpers.