linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Kitt <steve@sk2.org>
To: Andrew Morton <akpm@linux-foundation.org>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix references to nommu-mmap.rst
Date: Fri, 11 Sep 2020 21:10:26 +0200	[thread overview]
Message-ID: <20200911211026.349af8bd@heffalump.sk2.org> (raw)
In-Reply-To: <20200812092230.27541-1-steve@sk2.org>

[-- Attachment #1: Type: text/plain, Size: 2295 bytes --]

Hi,

This is still relevant as far as I can tell; master and docs-next still have
references to the old nommu-mmap.rst.

Regards,

Stephen

On Wed, 12 Aug 2020 11:22:30 +0200, Stephen Kitt <steve@sk2.org> wrote:
> nommu-mmap.rst was moved to Documentation/admin-guide/mm; this patch
> updates the remaining stale references to Documentation/mm.
> 
> Fixes: 800c02f5d030 ("docs: move nommu-mmap.txt to admin-guide and rename to ReST")
> Signed-off-by: Stephen Kitt <steve@sk2.org>
> ---
>  init/Kconfig | 2 +-
>  mm/Kconfig   | 2 +-
>  mm/nommu.c   | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/init/Kconfig b/init/Kconfig
> index 2dd5531dae98..8d5fefd1f229 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -1957,7 +1957,7 @@ config MMAP_ALLOW_UNINITIALIZED
>  	  userspace.  Since that isn't generally a problem on no-MMU systems,
>  	  it is normally safe to say Y here.
> 
> -	  See Documentation/mm/nommu-mmap.rst for more information.
> +	  See Documentation/admin-guide/mm/nommu-mmap.rst for more information.
> 
> config SYSTEM_DATA_VERIFICATION
>  	def_bool n
> diff --git a/mm/Kconfig b/mm/Kconfig
> index d41f3fa7e923..29e239497718 100644
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -387,7 +387,7 @@ config NOMMU_INITIAL_TRIM_EXCESS
>  	  This option specifies the initial value of this option.  The default
>  	  of 1 says that all excess pages should be trimmed.
>  
> -	  See Documentation/mm/nommu-mmap.rst for more information.
> +	  See Documentation/admin-guide/mm/nommu-mmap.rst for more information. 
> 
> config TRANSPARENT_HUGEPAGE
>  	bool "Transparent Hugepage Support"
> diff --git a/mm/nommu.c b/mm/nommu.c
> index 64539971188b..e8e2c5bb6f0a 100644
> --- a/mm/nommu.c
> +++ b/mm/nommu.c
> @@ -5,7 +5,7 @@
>   *  Replacement code for mm functions to support CPU's that don't
>   *  have any form of memory management unit (thus no virtual memory).
>   *
> - *  See Documentation/mm/nommu-mmap.rst
> + *  See Documentation/admin-guide/mm/nommu-mmap.rst
>   *
>   *  Copyright (c) 2004-2008 David Howells <dhowells@redhat.com>
>   *  Copyright (c) 2000-2003 David McCullough <davidm@snapgear.com>
> 
> base-commit: e176b7a3054eef44a22f6ca3d14168dcf9bad21e
> -- 
> 2.20.1
> 

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-09-11 19:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12  9:22 [PATCH] Fix references to nommu-mmap.rst Stephen Kitt
2020-09-11 19:10 ` Stephen Kitt [this message]
2020-09-24 17:04 ` Jonathan Corbet

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=20200911211026.349af8bd@heffalump.sk2.org \
    --to=steve@sk2.org \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mchehab+huawei@kernel.org \
    /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).