[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191021014336.14030-1-chris.packham@alliedtelesis.co.nz>
Date: Mon, 21 Oct 2019 14:43:36 +1300
From: Chris Packham <chris.packham@...iedtelesis.co.nz>
To: corbet@....net
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
trivial@...nel.org,
Chris Packham <chris.packham@...iedtelesis.co.nz>
Subject: [PATCH] docs: ioctl: fix typo
"pointres" should be "pointers".
Signed-off-by: Chris Packham <chris.packham@...iedtelesis.co.nz>
---
Documentation/ioctl/botching-up-ioctls.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ioctl/botching-up-ioctls.rst b/Documentation/ioctl/botching-up-ioctls.rst
index ac697fef3545..2d4829b2fb09 100644
--- a/Documentation/ioctl/botching-up-ioctls.rst
+++ b/Documentation/ioctl/botching-up-ioctls.rst
@@ -46,7 +46,7 @@ will need to add a 32-bit compat layer:
conversion or worse, fiddle the raw __u64 through your code since that
diminishes the checking tools like sparse can provide. The macro
u64_to_user_ptr can be used in the kernel to avoid warnings about integers
- and pointres of different sizes.
+ and pointers of different sizes.
Basics
--
2.23.0
Powered by blists - more mailing lists