10 Commits

Author	SHA1	Message	Date
Kevin Lo	4b29020487	Initialize T1 to silent gcc warning. ... Approved by: cognet	2006-10-22 02:19:33 +00:00
Alexander Kabaev	bcbd3d69bf	GCC 3.4.6 gets confused on this file and produces bogus warning. ... Shut it up.	2006-08-26 21:48:00 +00:00
Poul-Henning Kamp	5fdd8d28a3	Correctly bzero the entire context, not just the first sizeof(void *) bytes. ... Found by: Juergen Buchmueller <pullmoll@stop1984.com>	2003-09-08 18:32:33 +00:00
David E. O'Brien	ad39da7821	Use __FBSDID().	2003-06-10 21:44:29 +00:00
Poul-Henning Kamp	ba459bd472	Make this compilable from userland as well.	2002-11-01 08:56:39 +00:00
Mark Murray	d56fb9ceb0	Fix some really pedantic GCC warnings.	2002-07-15 13:45:15 +00:00
Alfred Perlstein	14e10f9952	Remove __P.	2002-03-20 05:14:42 +00:00
Hajimu UMEMOTO	e8647cfc81	off by one error in Aaron Gifford's code. KAME PR 393. ... PR: kern/34242 Submitted by: Aaron D. Gifford <agifford@infowest.com> MFC after: 1 week	2002-02-26 16:58:58 +00:00
Hajimu UMEMOTO	c56df4e782	less warning ... warning: cast discards qualifiers from pointer target type	2001-06-16 19:32:37 +00:00
Hajimu UMEMOTO	3384154590	Sync with recent KAME. ... This work was based on kame-20010528-freebsd43-snap.tgz and some critical problem after the snap was out were fixed. There are many many changes since last KAME merge. TODO: - The definitions of SADB_* in sys/net/pfkeyv2.h are still different from RFC2407/IANA assignment because of binary compatibility issue. It should be fixed under 5-CURRENT. - ip6po_m member of struct ip6_pktopts is no longer used. But, it is still there because of binary compatibility issue. It should be removed under 5-CURRENT. Reviewed by: itojun Obtained from: KAME MFC after: 3 weeks	2001-06-11 12:39:29 +00:00