David Brownell af9379c712 documentation: when to BUG(), and when to not BUG() ... Provide some basic advice about when to use BUG()/BUG_ON(): never, unless there's really no better option. This matches my understanding of the standard policy ... which seems not to be written down so far, outside of LKML messages that I haven't bookmarked. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Cc: Hans Verkuil <hverkuil@xs4all.nl> Cc: Ingo Molnar <mingo@elte.hu> Cc: Arjan van de Ven <arjan@infradead.org> Cc: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2009-01-06 15:59:13 -08:00
..
acpi
asm-arm
asm-frv	atomic_t: unify all arch definitions	2009-01-06 15:59:10 -08:00
asm-generic	documentation: when to BUG(), and when to not BUG()	2009-01-06 15:59:13 -08:00
asm-h8300
asm-m32r	atomic_t: unify all arch definitions	2009-01-06 15:59:10 -08:00
asm-m68k	atomic_t: unify all arch definitions	2009-01-06 15:59:10 -08:00
asm-mn10300	atomic_t: unify all arch definitions	2009-01-06 15:59:10 -08:00
asm-xtensa	atomic_t: unify all arch definitions	2009-01-06 15:59:10 -08:00
crypto
drm
keys
linux	poll: allow f_op->poll to sleep	2009-01-06 15:59:12 -08:00
math-emu
media
mtd
net	ipv6: Fix sporadic sendmsg -EINVAL when sending to multicast groups.	2009-01-04 16:04:39 -08:00
pcmcia
rdma
rxrpc
scsi
sound
trace
video
xen
Kbuild