5 commits

Author	SHA1	Message	Date
Pedro F. Giffuni	5eadfbfcd0	libbluetooth: use NULL instead of zero for pointers.	2016-04-18 14:41:30 +00:00
Takanori Watanabe	8d6f425ddd	Check l2cap socket initialisation and define L2CAP_SOCKET_CHECKED ... This will fix build.	2015-04-07 16:48:23 +00:00
Maksim Yevmenkin	baeef61449	Add Bluetooth compatibility shims. Inspired by Linux BlueZ and NetBSD. ... Discussed with: Iain Hibbert plunky -at- rya-online -dot- net of NetBSD MFC after: 1 month	2009-03-06 23:30:07 +00:00
Mark Murray	16fc3635f7	Make NULL a (void*)0 whereever possible, and fix the warnings(-Werror) ... that this provokes. "Wherever possible" means "In the kernel OR NOT C++" (implying C). There are places where (void *) pointers are not valid, such as for function pointers, but in the special case of (void *)0, agreement settles on it being OK. Most of the fixes were NULL where an integer zero was needed; many of the fixes were NULL where ascii <nul> ('\0') was needed, and a few were just "other". Tested on: i386 sparc64	2004-03-05 08:10:19 +00:00
Maksim Yevmenkin	0986ab12e4	Update Bluetooth code. ... Reviewed by: M. Warner Losh <imp@bsdimp.com>; John Hay <jhay@freebsd.org> Approved by: M. Warner Losh <imp@bsdimp.com> (mentor)	2003-10-12 22:04:24 +00:00