From: Jonathan Corbet <corbet@lwn.net>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/3] Better organize the core-api manual
Date: Mon, 2 Mar 2020 16:23:47 -0700 [thread overview]
Message-ID: <20200302162347.65dc3709@lwn.net> (raw)
In-Reply-To: <202003021456.F173F9DFC7@keescook>
On Mon, 2 Mar 2020 14:59:43 -0800
Kees Cook <keescook@chromium.org> wrote:
> Random thought while looking through it: there's
> stuff in the driver-api that seems like maybe it should move into the
> core (e.g. Documentation/driver-api/basics.rst) but I'm not sure what
> the line between "core" and "driver" is. I would think the "driver API"
> docs should be driver-specific, in which case much of basics.rst should
> be moved into "core".
Sigh...driver-api is, of course, an even bigger mess than core-api. I
mean to delve into it and create some order there as well, when I get a
chance.
The original idea was that driver-api would contain stuff you need to know
if you're writing drivers but can ignore otherwise. We can always rethink
that, of course.
Thanks,
jon
prev parent reply other threads:[~2020-03-02 23:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 22:39 [PATCH 0/3] Better organize the core-api manual Jonathan Corbet
2020-03-02 22:39 ` [PATCH 1/3] docs: Organize core-api/index.rst Jonathan Corbet
2020-03-02 22:39 ` [PATCH 2/3] docs: move gcc-plugins to the kbuild manual Jonathan Corbet
2020-03-05 2:12 ` Masahiro Yamada
2020-03-02 22:39 ` [PATCH 3/3] docs: move core-api/ioctl.rst to driver-api/ Jonathan Corbet
2020-03-02 22:59 ` [PATCH 0/3] Better organize the core-api manual Kees Cook
2020-03-02 23:23 ` Jonathan Corbet [this message]
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=20200302162347.65dc3709@lwn.net \
--to=corbet@lwn.net \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
/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).