Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 26 Jun 2018 08:42:39 -0600
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
Message-ID: <20180626084239.27d88f7e@lwn.net>
In-Reply-To: <20180622073211.8220-1-martink@posteo.de>
References: <20180622073211.8220-1-martink@posteo.de>
Organization: LWN.net
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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