* [PATCH] Documentation: nommu-map: Fix duplicate word typo
@ 2018-06-22 7:32 Martin Kepplinger
2018-06-26 14:42 ` Jonathan Corbet
0 siblings, 1 reply; 2+ messages in thread
From: Martin Kepplinger @ 2018-06-22 7:32 UTC (permalink / raw)
To: corbet; +Cc: linux-doc, linux-kernel, Martin Kepplinger
Signed-off-by: Martin Kepplinger <martink@posteo.de>
---
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] Documentation: nommu-map: Fix duplicate word typo
2018-06-22 7:32 [PATCH] Documentation: nommu-map: Fix duplicate word typo Martin Kepplinger
@ 2018-06-26 14:42 ` Jonathan Corbet
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Corbet @ 2018-06-26 14:42 UTC (permalink / raw)
To: Martin Kepplinger; +Cc: linux-doc, linux-kernel
On Fri, 22 Jun 2018 09:32:11 +0200
Martin Kepplinger <martink@posteo.de> wrote:
> Signed-off-by: Martin Kepplinger <martink@posteo.de>
> ---
> 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-06-26 14:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-06-22 7:32 [PATCH] Documentation: nommu-map: Fix duplicate word typo Martin Kepplinger
2018-06-26 14:42 ` 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).