linux-kernel - can we use mandatory-y for non-uapi headers?

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-next>] [day] [month] [year] [list]

Message-ID: <20190810075226.GA24085@lst.de>
Date:   Sat, 10 Aug 2019 09:52:26 +0200
From:   Christoph Hellwig <hch@....de>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc:     linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: can we use mandatory-y for non-uapi headers?

Hi Masahiro,

what is the reason that the documentation says mandatory-y should only
be used for uapi headers?  If would also be very useful for normal
asm-generic headers where most people use the generic version and we
only have a few overrides.  Two headers that immediately come to mind
are dma-mapping.h, or msi.h.