linux-kernel - Re: [PATCH 0/3] Better organize the core-api manual

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 2 Mar 2020 16:23:47 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Kees Cook <keescook@...omium.org>
Cc:     linux-kernel@...r.kernel.org,
        Masahiro Yamada <masahiroy@...nel.org>,
        Michal Marek <michal.lkml@...kovi.net>,
        linux-doc@...r.kernel.org
Subject: Re: [PATCH 0/3] Better organize the core-api manual

On Mon, 2 Mar 2020 14:59:43 -0800
Kees Cook <keescook@...omium.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