Decnet exposes itself to proc and packets before it has finished initializing.
This was always a race, but the notifier replay might expose it worse.

Patch from Russell King.

into nuts.ninka.net:/disk1/davem/BK/net-2.6

This patch updates the CREDITS and MAINTAINERS files to reflect the change
of the maintainer role for the Bluetooth subsystem.

If the inquiry cache is empty it makes no sense to return zero number of
inquiry result even if the age of cache is not outdated.

The L2CAP reference counting must be increased by the RFCOMM module if an
incoming connection is accepted. If this is not done, it will be decreased
one time to often if the connection is terminated.

Otherwise this can lead to the BUG_TRAP in __xfrm_state_destroy when
xfrm_state_put() finds this is the last reference.

- the found or allocated xfrm_states are not passed correctly to
  xfrm_bundle_create (and to the subsequent frees in case of create
  failing) if the first xfrm_tmpl_resolve failed and the second one
  succeeded.
- error handling is wrong.

Otherwise we can trigger the BUG trap in __xfrm_state_destroy() when
xfrm_state_put() finds this is the last reference.

Remove duplicate/conflicting code
now that netdev_register_notifier replays the device registration events.

Remove duplicate/conflicting code now that netdev_register_notifier replays the
device registration events. Reorder initialization to avoid having to simplify error unwind
if /proc creation failed.

Remove duplicate/conflicting code 
now that netdev_register_notifier replays the device registration events.

Change IPV6 to handle the new case where netdev events are replayed on registration:
* change code ordering so address configuration is ready before registration
  (this was actually a bug in existing code)
* take out code that capture's existing devices, this is now done in the replay
* make notifier code local to addrconf.c so it can be have smaller scope

In general a Bluetooth stack that creates an ACL link should also take
care of its termination, but some Bluetooth devices think otherwise. The
problem is that the Bluetooth specification don't defines an ownership
of an ACL link and if nobody cares about it, two devices stay connected
even if there is no need. To avoid leftover ACL links the disconnect
timer must also be used for incoming connections, but it is set twice
the default disconnect timeout so the other side get enough time to
clean everything by itself.

The only possible default value for pscan_rep_mode, if there is no entry
in the inquiry cache, can be R2.

This patch fixes the module reference counting which was done wrong while
porting this driver to the 2.6 kernel series.

to generate the duplicate area at 0x0000 and 0x100000.

There's no downside to it, so allow it even though it's
a tad strange.

into home.osdl.org:/home/torvalds/v2.5/linux

Spotted by Matteo Croce 

into home.osdl.org:/home/torvalds/v2.5/linux