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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: usage of linux/types.h wrt to install_headers
    • From: Adrian Bunk <[email protected]>

• Prev by Date: Re: [PATCH] OMAP: I2C driver for TI OMAP boards #3
• Next by Date: dentry cache grows to really large number on 64bit machine
• Previous by thread: [PATCH] ARM: OMAP: cleanup long lines in sx1 mixer
• Next by thread: Re: usage of linux/types.h wrt to install_headers
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]