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:	Wed, 6 Dec 2006 18:03:50 -0500
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: usage of linux/types.h wrt to install_headers

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 ...
-mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ