Re: usage of linux/types.h wrt to install_headers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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>.

> -mike

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
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/

[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]
  Powered by Linux