- 28 Apr, 2003 6 commits
-
-
Stephen Hemminger authored
* Need _rcu on the list_for_each_entry in br_get_port because called in read path for some ioctls * Move two small functions is_root_bridge and is_designated_port into inlines because they are so short.
-
Stephen Hemminger authored
-
Bart De Schuymer authored
-
Stephen Hemminger authored
-
Steven Cole authored
-
bk://kernel.bkbits.net/acme/net-2.5David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/net-2.5
-
- 29 Apr, 2003 2 commits
-
-
Arnaldo Carvalho de Melo authored
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.
-
Arnaldo Carvalho de Melo authored
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.
-
- 28 Apr, 2003 23 commits
-
-
Arnaldo Carvalho de Melo authored
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.
-
Arnaldo Carvalho de Melo authored
. 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).
-
Arnaldo Carvalho de Melo authored
. 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.
-
bk://kernel.bkbits.net/acme/net-2.5David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/net-2.5
-
bk://kernel.bkbits.net/acme/net-2.5David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/net-2.5
-
bk://kernel.bkbits.net/acme/net-2.5David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/net-2.5
-
Arnaldo Carvalho de Melo authored
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.
-
bk://kernel.bkbits.net/acme/net-2.5David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/net-2.5
-
David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/net-2.5
-
Arnaldo Carvalho de Melo authored
-
Arnaldo Carvalho de Melo authored
-
Arnaldo Carvalho de Melo authored
-
Arnaldo Carvalho de Melo authored
-
Arnaldo Carvalho de Melo authored
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.
-
Arnaldo Carvalho de Melo authored
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.
-
Arnaldo Carvalho de Melo authored
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.
-
Arnaldo Carvalho de Melo authored
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.
-
Arnaldo Carvalho de Melo authored
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.
-
Arnaldo Carvalho de Melo authored
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.
-
Arnaldo Carvalho de Melo authored
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.
-
Arnaldo Carvalho de Melo authored
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.
-
Arnaldo Carvalho de Melo authored
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.
-
bk://kernel.bkbits.net/acme/net-2.5David S. Miller authored
into nuts.ninka.net:/home/davem/src/BK/net-2.5
-
- 27 Apr, 2003 9 commits
-
-
Arnaldo Carvalho de Melo authored
-
Arnaldo Carvalho de Melo authored
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.
-
David S. Miller authored
-
David S. Miller authored
-
Rusty Russell authored
Adds an owner field to nf_hook_ops, and use it to hold the hook in place for queued packets.
-
David S. Miller authored
into kernel.bkbits.net:/home/davem/net-2.5
-
David S. Miller authored
-
David S. Miller authored
-
David S. Miller authored
-