Re: [PATCH] s/u64/__u64/ in linux/xfrm.h

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

 



>    From: Jeff Garzik <jgarzik@pobox.com>
>    Date: Mon, 02 Jun 2003 21:14:25 -0400
>
>    As is evident from (a) include/linux standard policy and (b) patches
> applied to CryptoAPI in the past, we should be using kernel standard
> types:  u64, not __u64.
>
> Becuase u64 is not defined when __KERNEL__ is not defined, these are user
> visible headers.
>
> User apps will include this file, and I am not willing to even discuss not
> letting them do so.

Hooray.  I agree with that kind of reality.

Dave, what other linux networking headers are acceptable for user apps
to include?  If you don't mind answering.
Maybe netlink.h, rtnetlink.h?

~Randy



-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux