From: Jessica Yu <jeyu@kernel.org>
To: Matthias Maennich <maennich@google.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Adam Zerella <adam.zerella@gmail.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 10:12:42 +0200 [thread overview]
Message-ID: <20191007081241.GA8279@linux-8ccs> (raw)
In-Reply-To: <20191007060614.GA142813@google.com>
+++ Matthias Maennich [07/10/19 07:06 +0100]:
>Hi!
>
>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.
>>
>>I am not sure if this is the perfect place, but I added its index
>>close to the module-signing.
>
>When searching for a place for this documentation, kbuild/ was the
>closest I could find. admin-guide/ seems to target system administrators
>while the symbol namespace feature documentation is relevant for kernel
>developers. I am ok to take maintainership for the file, but the new
>location suggested seems not to be a good fit either.
This was my line of thought as well, since the audience of
admin-guide/ is sysadmins and users. Namespaces are mostly relevant to
module authors and kernel developers. Currently, I don't think there
is an existing good place in Documentation/ for this topic :-/
I suppose kernel-hacking/ might be the closest fit, as Adam suggested.
Thanks,
Jessica
next prev parent reply other threads:[~2019-10-07 8:12 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
2019-10-07 6:06 ` Matthias Maennich
2019-10-07 8:12 ` Jessica Yu [this message]
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=20191007081241.GA8279@linux-8ccs \
--to=jeyu@kernel.org \
--cc=adam.zerella@gmail.com \
--cc=corbet@lwn.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.