linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Zerella <adam.zerella@gmail.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Jessica Yu <jeyu@kernel.org>,
	Matthias Maennich <maennich@google.com>,
	Michal Marek <michal.lkml@markovi.net>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] doc: move namespaces.rst out of kbuild directory
Date: Mon, 7 Oct 2019 16:59:26 +1100	[thread overview]
Message-ID: <20191007055926.GA9631@gmail.com> (raw)
In-Reply-To: <20191007043611.31036-1-yamada.masahiro@socionext.com>

On Mon, Oct 07, 2019 at 01:36:11PM +0900, Masahiro Yamada wrote:
> I did not notice this document was added to Documentation/kbuild/,
> and I do not understand how it is related to the build system.
> 
> Kick it out of the kbuild directory.

Should we delete the file entirely or does it belong somewhere else? It
was added in c4f4af4094d6c7dbca3acd8d04df2759d268a116 and is referenced
in `Documentation/kernel-hacking/hacking.rst`.

Can we put into the `kernel-hacking` directory?

> I am not sure if this is the perfect place, but I added its index
> close to the module-signing.
> 
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
> 
>  Documentation/admin-guide/index.rst                  | 1 +
>  Documentation/{kbuild => admin-guide}/namespaces.rst | 0
>  MAINTAINERS                                          | 1 +
>  3 files changed, 2 insertions(+)
>  rename Documentation/{kbuild => admin-guide}/namespaces.rst (100%)
> 
> diff --git a/Documentation/admin-guide/index.rst b/Documentation/admin-guide/index.rst
> index 34cc20ee7f3a..ca632fda700f 100644
> --- a/Documentation/admin-guide/index.rst
> +++ b/Documentation/admin-guide/index.rst
> @@ -65,6 +65,7 @@ configure specific aspects of kernel behavior to your liking.
>     parport
>     md
>     module-signing
> +   namespaces
>     rapidio
>     sysrq
>     unicode
> diff --git a/Documentation/kbuild/namespaces.rst b/Documentation/admin-guide/namespaces.rst
> similarity index 100%
> rename from Documentation/kbuild/namespaces.rst
> rename to Documentation/admin-guide/namespaces.rst
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 55199ef7fa74..91815dcc5914 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -11547,6 +11547,7 @@ NSDEPS
>  M:	Matthias Maennich <maennich@google.com>
>  S:	Maintained
>  F:	scripts/nsdeps
> +F:	Documentation/admin-guide/namespaces.rst
>  
>  NTB AMD DRIVER
>  M:	Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
> -- 
> 2.17.1
> 

  reply	other threads:[~2019-10-07  5:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07  4:36 [PATCH] doc: move namespaces.rst out of kbuild directory Masahiro Yamada
2019-10-07  5:59 ` Adam Zerella [this message]
2019-10-07  6:06 ` Matthias Maennich
2019-10-07  8:12   ` Jessica Yu
2019-10-07 13:29     ` Jonathan Corbet
2019-10-07 13:41       ` Matthias Maennich
2019-10-07 16:58         ` Randy Dunlap

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=20191007055926.GA9631@gmail.com \
    --to=adam.zerella@gmail.com \
    --cc=corbet@lwn.net \
    --cc=jeyu@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maennich@google.com \
    --cc=mchehab@kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=yamada.masahiro@socionext.com \
    /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).