| /freebsd/sys/netgraph/bluetooth/include/ |
| H A D | ng_btsocket_sco.h | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | ng_btsocket_hci_raw.h | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | ng_btsocket_l2cap.h | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | ng_btsocket_rfcomm.h | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| /freebsd/sys/netinet/ |
| H A D | sctp_module.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | udp_var.h | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | sctp_var.h | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | in_proto.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | ip_var.h | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | ip_divert.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| /freebsd/sys/dev/hyperv/hvsock/ |
| H A D | hv_sock.h | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | hv_sock.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| /freebsd/share/man/man9/ |
| H A D | domain.9 | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| /freebsd/sys/netgraph/bluetooth/socket/ |
| H A D | ng_btsocket_sco.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | ng_btsocket.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | ng_btsocket_l2cap_raw.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | ng_btsocket_hci_raw.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | ng_btsocket_l2cap.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | ng_btsocket_rfcomm.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| /freebsd/sys/kern/ |
| H A D | uipc_debug.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | uipc_domain.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| /freebsd/sys/netipsec/ |
| H A D | keysock.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| /freebsd/sys/sys/ |
| H A D | protosw.h | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| /freebsd/sys/netinet6/ |
| H A D | ip6_var.h | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|
| H A D | in6_proto.c | diff 89128ff3e42196c8b41a3c59f7a2d95c0a4ac0ee Mon Jan 03 19:15:21 CET 2022 Gleb Smirnoff <glebius@FreeBSD.org> protocols: init with standard SYSINIT(9) or VNET_SYSINIT
The historical BSD network stack loop that rolls over domains and
over protocols has no advantages over more modern SYSINIT(9).
While doing the sweep, split global and per-VNET initializers.
Getting rid of pr_init allows to achieve several things:
o Get rid of ifdef's that protect against double foo_init() when
both INET and INET6 are compiled in.
o Isolate initializers statically to the module they init.
o Makes code easier to understand and maintain.
Reviewed by: melifaro
Differential revision: https://reviews.freebsd.org/D33537
|