2018-06-22 07:33:24

by Martin Kepplinger

Subject: [PATCH] Documentation: nommu-map: Fix duplicate word typo

Signed-off-by: Martin Kepplinger <[email protected]>
---
Documentation/nommu-mmap.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/nommu-mmap.txt b/Documentation/nommu-mmap.txt
index 69556f0d494b..530fed08de2c 100644
--- a/Documentation/nommu-mmap.txt
+++ b/Documentation/nommu-mmap.txt
@@ -47,7 +47,7 @@ and it's also much more restricted in the latter case:
appropriate mapping protection capabilities. Ramfs, romfs, cramfs
and mtd might all permit this.

- - If the backing device device can't or won't permit direct sharing,
+ - If the backing device can't or won't permit direct sharing,
but does have the NOMMU_MAP_COPY capability, then a copy of the
appropriate bit of the file will be read into a contiguous bit of
memory and any extraneous space beyond the EOF will be cleared
--
2.17.1

2018-06-26 16:05:02

by Jonathan Corbet

Subject: Re: [PATCH] Documentation: nommu-map: Fix duplicate word typo

On Fri, 22 Jun 2018 09:32:11 +0200
Martin Kepplinger <[email protected]> wrote:

> Signed-off-by: Martin Kepplinger <[email protected]>
> ---
> Documentation/nommu-mmap.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/nommu-mmap.txt b/Documentation/nommu-mmap.txt
> index 69556f0d494b..530fed08de2c 100644
> --- a/Documentation/nommu-mmap.txt
> +++ b/Documentation/nommu-mmap.txt
> @@ -47,7 +47,7 @@ and it's also much more restricted in the latter case:
> appropriate mapping protection capabilities. Ramfs, romfs, cramfs
> and mtd might all permit this.
>
> - - If the backing device device can't or won't permit direct sharing,
> + - If the backing device can't or won't permit direct sharing,
> but does have the NOMMU_MAP_COPY capability, then a copy of the
> appropriate bit of the file will be read into a contiguous bit of
> memory and any extraneous space beyond the EOF will be cleared

Applied, thanks.

jon