| /openbmc/linux/include/linux/ |
| H A D | genl_magic_func.h | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/ieee802154/ |
| H A D | netlink.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/netlabel/ |
| H A D | netlabel_cipso_v4.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | netlabel_mgmt.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | netlabel_unlabeled.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/hsr/ |
| H A D | hsr_netlink.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/tipc/ |
| H A D | netlink.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/kernel/ |
| H A D | taskstats.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/l2tp/ |
| H A D | l2tp_netlink.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/include/net/ |
| H A D | genetlink.h | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/ipv4/ |
| H A D | tcp_metrics.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/core/ |
| H A D | drop_monitor.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/nfc/ |
| H A D | netlink.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/netlink/ |
| H A D | genetlink.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/drivers/net/team/ |
| H A D | team.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/openvswitch/ |
| H A D | datapath.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/netfilter/ipvs/ |
| H A D | ip_vs_ctl.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/wireless/ |
| H A D | nl80211.c | diff c53ed7423619b4e8108914a9f31b426dd58ad591 Tue Nov 19 08:19:31 CST 2013 Johannes Berg <johannes.berg@intel.com> genetlink: only pass array to genl_register_family_with_ops()
As suggested by David Miller, make genl_register_family_with_ops()
a macro and pass only the array, evaluating ARRAY_SIZE() in the
macro, this is a little safer.
The openvswitch has some indirection, assing ops/n_ops directly in
that code. This might ultimately just assign the pointers in the
family initializations, saving the struct genl_family_and_ops and
code (once mcast groups are handled differently.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|