* [PATCH] docs: ioctl: fix typo
@ 2019-10-21 1:43 Chris Packham
2019-10-24 18:11 ` Jonathan Corbet
0 siblings, 1 reply; 2+ messages in thread
From: Chris Packham @ 2019-10-21 1:43 UTC (permalink / raw)
To: corbet; +Cc: linux-doc, linux-kernel, trivial, Chris Packham
"pointres" should be "pointers".
Signed-off-by: Chris Packham <chris.packham@alliedtelesis.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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] docs: ioctl: fix typo
2019-10-21 1:43 [PATCH] docs: ioctl: fix typo Chris Packham
@ 2019-10-24 18:11 ` Jonathan Corbet
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Corbet @ 2019-10-24 18:11 UTC (permalink / raw)
To: Chris Packham; +Cc: linux-doc, linux-kernel, trivial
On Mon, 21 Oct 2019 14:43:36 +1300
Chris Packham <chris.packham@alliedtelesis.co.nz> wrote:
> "pointres" should be "pointers".
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.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.
Applied, thanks.
jon
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-10-24 18:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-21 1:43 [PATCH] docs: ioctl: fix typo Chris Packham
2019-10-24 18:11 ` 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).