From: Jonathan Corbet <corbet@lwn.net>
To: Martin Kepplinger <martink@posteo.de>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: nommu-map: Fix duplicate word typo
Date: Tue, 26 Jun 2018 08:42:39 -0600 [thread overview]
Message-ID: <20180626084239.27d88f7e@lwn.net> (raw)
In-Reply-To: <20180622073211.8220-1-martink@posteo.de>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-06-26 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 7:32 [PATCH] Documentation: nommu-map: Fix duplicate word typo Martin Kepplinger
2018-06-26 14:42 ` Jonathan Corbet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180626084239.27d88f7e@lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martink@posteo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).