Thanks to Rusty for spotting this one, if the net family module is not there
anymore (or is going away at that time) it is not supported, not busy.

Thanks to Rusty for spotting this one, if the protocol module is not there
anymore (or is going away at that time) it is not supported, not busy.

With this the pppox module is protected by the networking core and
the pppox "core" protects modules for specific pppox protocols (pppoe,
for instance), while doing it removed some not needed struct sock
member initializations in pppoe_create that are done by sock_init_data.

. rename proto to pppox_protos, even being static this is too generic a name
. use rc as the name for result variables, just for consistency with other
  net sources

This is in preparation for having a proper net family module level modules
infrastructure, with the top level (af_pppox) doing the module refcounting
before calling any functions registered by the lower level protocol modules
(in this case just PPPOE for now).

. use switch/case alignment at the same column, 
  more common in the kernel sources
. remove outdated module refcounting comments
. have just one exit (return) in the ioctl functions
. use 'rc' for return variables, not ret or err, for
  consistency on naming.

  
Now the core networking infrastructure will (finally) do that for the net
protocol families, its just a matter of setting the ->owner field in the
registered struct net_proto_family to THIS_MODULE.

Now the core networking infrastructure will (finally) do that for the net
protocol families, its just a matter of setting the ->owner field in the
registered struct net_proto_family to THIS_MODULE.

Now the core networking infrastructure will (finally) do that for the net
protocol families, its just a matter of setting the ->owner field in the
registered struct net_proto_family to THIS_MODULE.

Now the core networking infrastructure will (finally) do that for the net
protocol families, its just a matter of setting the ->owner field in the
registered struct net_proto_family to THIS_MODULE.

Now the core networking infrastructure will (finally) do that for the net
protocol families, its just a matter of setting the ->owner field in the
registered struct net_proto_family to THIS_MODULE.

Now the core networking infrastructure will (finally) do that for the net
protocol families, its just a matter of setting the ->owner field in the
registered struct net_proto_family to THIS_MODULE.

Now the core networking infrastructure will (finally) do that for the net
protocol families, its just a matter of setting the ->owner field in the
registered struct net_proto_family to THIS_MODULE.

Now the core networking infrastructure will (finally) do that for the net
protocol families, its just a matter of setting the ->owner field in the
registered struct net_proto_family to THIS_MODULE.

Now the core networking infrastructure will (finally) do that for the net
protocol families, its just a matter of setting the ->owner field in the
registered struct net_proto_family to THIS_MODULE.

Now the core networking infrastructure will (finally) do that for the net
protocol families, its just a matter of setting the ->owner field in the
registered struct net_proto_family to THIS_MODULE.

Now the core networking infrastructure will (finally) do that for the net
protocol families, its just a matter of setting the ->owner field in the
registered struct net_proto_family to THIS_MODULE.

Now the core networking infrastructure will (finally) do that for the net
protocol families, its just a matter of setting the ->owner field in the
registered struct net_proto_family to THIS_MODULE.

The previous changeset for llc was enough when the BSD sockets interface
for AF_LLC was not selected, but this changeset is needed when it is
selected.

Now the core networking infrastructure will (finally) do that for the net
protocol families, its just a matter of setting the ->owner field in the
registered struct net_proto_family to THIS_MODULE.

Now the core networking infrastructure will (finally) do that for the net protocol
families, its just a matter of setting the ->owner field in the registered struct
net_proto_family to THIS_MODULE.

  
Thanks to Max Krasnyansky for spotting this.

into home.transmeta.com:/home/torvalds/v2.5/linux

readonly dos attribute in mode when server does not support
CIFS Unix extensions.  Fix abbreviated readdir to servers that
do support CIFS Unix extensions.

Every 64-bit architecture changes the end of iomem_resources. Some more
gracefully than others. This patch does away with all that by making
it end at ~0UL by default.

at cleanups.

into home.transmeta.com:/home/torvalds/v2.5/linux

It's the last file of the scsi core that needed to be converted from
the old scsi style.

Patch against current scsi-misc-2.5 tree.

Remove the scsi EVPD code.

Set the sysfs name to the form "SCSI scsi-type".

but the build was confused by the fact that they did share some files.

Move INITRD code from do_mounts_rd.c to new file do_mounts_initrd.c.