Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH] doc: remove stray HTML entity in '<slash>'
To:     Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
        Jonathan Corbet <corbet@lwn.net>
Cc:     linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
References: <20200729021120.35901-1-luc.vanoostenryck@gmail.com>
From:   Randy Dunlap <rdunlap@infradead.org>
Message-ID: <1faef34e-053a-121f-1dc5-333c6b6539cc@infradead.org>
Date:   Tue, 28 Jul 2020 19:14:49 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <20200729021120.35901-1-luc.vanoostenryck@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 7/28/20 7:11 PM, Luc Van Oostenryck wrote:
> An excerpt from POSIX contains three occurrences of '<slash>' but
> the first two are spelled starting with an HTML entity: '&lt;slash>'
> 
> Fix this by replacing the stray HTML entity by a '<'.
> 
> Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>

Hi Luc,
One day late.
Fixed and merged yesterday.

https://lore.kernel.org/linux-doc/20200727114527.23944-1-vegard.nossum@oracle.com/


> ---
>  Documentation/filesystems/path-lookup.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/filesystems/path-lookup.rst b/Documentation/filesystems/path-lookup.rst
> index e2ba15146365..d46688d6770d 100644
> --- a/Documentation/filesystems/path-lookup.rst
> +++ b/Documentation/filesystems/path-lookup.rst
> @@ -78,8 +78,8 @@ particular, ``mkdir()`` and ``rmdir()`` each create or remove a directory named
>  by the final component, and they are required to work with pathnames
>  ending in "``/``".  According to POSIX_
>  
> -  A pathname that contains at least one non- &lt;slash> character and
> -  that ends with one or more trailing &lt;slash> characters shall not
> +  A pathname that contains at least one non-<slash> character and
> +  that ends with one or more trailing <slash> characters shall not
>    be resolved successfully unless the last pathname component before
>    the trailing <slash> characters names an existing directory or a
>    directory entry that is to be created for a directory immediately
> 

cheers.
-- 
~Randy