Linux-man Archive on lore.kernel.org
 help / color / Atom feed
* [PATCH] memfd_create.2: fix typos
@ 2019-10-30 22:39 Mike Rapoport
  2019-10-30 22:40 ` Mike Rapoport
  0 siblings, 1 reply; 2+ messages in thread
From: Mike Rapoport @ 2019-10-30 22:39 UTC (permalink / raw)
  To: Michael Kerrisk; +Cc: linux-man, Mike Rapoport

Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
---
 man2/memfd_create.2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/man2/memfd_create.2 b/man2/memfd_create.2
index 15b1362..9be8f3c 100644
--- a/man2/memfd_create.2
+++ b/man2/memfd_create.2
@@ -221,7 +221,7 @@ used with the file-sealing APIs provided by
 .PP
 The
 .BR memfd_create ()
-system call also has uses without file sealing
+system call also have uses without file sealing
 (which is why file-sealing is disabled, unless explicitly requested with the
 .BR MFD_ALLOW_SEALING
 flag).
@@ -254,7 +254,7 @@ signal.)
 Dealing with untrusted peers imposes extra complexity on
 code that employs shared memory.
 Memory sealing enables that extra complexity to be eliminated,
-by allowing a process to operate secure in the knowledge that
+by allowing a process to operate securely in the knowledge that
 its peer can't modify the shared memory in an undesired fashion.
 .PP
 An example of the usage of the sealing mechanism is as follows:
-- 
2.7.4


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

* Re: [PATCH] memfd_create.2: fix typos
  2019-10-30 22:39 [PATCH] memfd_create.2: fix typos Mike Rapoport
@ 2019-10-30 22:40 ` Mike Rapoport
  0 siblings, 0 replies; 2+ messages in thread
From: Mike Rapoport @ 2019-10-30 22:40 UTC (permalink / raw)
  To: Michael Kerrisk; +Cc: linux-man

On Wed, Oct 30, 2019 at 11:39:18PM +0100, Mike Rapoport wrote:
> Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
>  man2/memfd_create.2 | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/man2/memfd_create.2 b/man2/memfd_create.2
> index 15b1362..9be8f3c 100644
> --- a/man2/memfd_create.2
> +++ b/man2/memfd_create.2
> @@ -221,7 +221,7 @@ used with the file-sealing APIs provided by
>  .PP
>  The
>  .BR memfd_create ()
> -system call also has uses without file sealing
> +system call also have uses without file sealing

Oops, somehow I've misread it as "can has uses" :(

>  (which is why file-sealing is disabled, unless explicitly requested with the
>  .BR MFD_ALLOW_SEALING
>  flag).
> @@ -254,7 +254,7 @@ signal.)
>  Dealing with untrusted peers imposes extra complexity on
>  code that employs shared memory.
>  Memory sealing enables that extra complexity to be eliminated,
> -by allowing a process to operate secure in the knowledge that
> +by allowing a process to operate securely in the knowledge that
>  its peer can't modify the shared memory in an undesired fashion.
>  .PP
>  An example of the usage of the sealing mechanism is as follows:
> -- 
> 2.7.4
> 

-- 
Sincerely yours,
Mike.


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

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-30 22:39 [PATCH] memfd_create.2: fix typos Mike Rapoport
2019-10-30 22:40 ` Mike Rapoport

Linux-man Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-man/0 linux-man/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-man linux-man/ https://lore.kernel.org/linux-man \
		linux-man@vger.kernel.org
	public-inbox-index linux-man

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-man


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git