linux-kernel - [patch] include linux/types.h in a bunch of header files for usage with install

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]

Date:	Fri, 15 Dec 2006 21:08:50 -0500
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	"Adrian Bunk" <bunk@...sta.de>
Cc:	linux-kernel@...r.kernel.org
Subject: [patch] include linux/types.h in a bunch of header files for usage with install_headers

On 12/12/06, Adrian Bunk <bunk@...sta.de> wrote:
> On Wed, Dec 06, 2006 at 06:03:50PM -0500, Mike Frysinger wrote:
> > there are a plethora of headers that cannot be included straight due
> > to the usage of __ types (like __u32) without first including
> > linux/types.h ... so the question is, should all of these headers be
> > fixed to properly pull in linux/types.h first or are users expected to
> > "just know" the correct order of headers ?  in my mind, pretty much
> > every header is fair game for straight "#include <header>" usage and
> > requiring a list of headers to be pulled in properly is ignoring the
> > problem ...
>
> Yes, they should all be fixed to #include <linux/types.h>.

thanks, mondo patch attached :)
-mike

Download attachment "linux-include-types-header.patch" of type "application/octet-stream" (17662 bytes)