Searched hist:ff4c92d85c6f2777d2067f8552e7fefb4d1754ae (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/include/net/ |
| H A D | genetlink.h | diff ff4c92d85c6f2777d2067f8552e7fefb4d1754ae Mon Oct 04 14:14:03 CDT 2010 Johannes Berg <johannes.berg@intel.com> genetlink: introduce pre_doit/post_doit hooks
Each family may have some amount of boilerplate
locking code that applies to most, or even all,
commands.
This allows a family to handle such things in
a more generic way, by allowing it to
a) include private flags in each operation
b) specify a pre_doit hook that is called,
before an operation's doit() callback and
may return an error directly,
c) specify a post_doit hook that can undo
locking or similar things done by pre_doit,
and finally
d) include two private pointers in each info
struct passed between all these operations
including doit(). (It's two because I'll
need two in nl80211 -- can be extended.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Acked-by: David S. Miller <davem@davemloft.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
| /openbmc/linux/net/netlink/ |
| H A D | genetlink.c | diff ff4c92d85c6f2777d2067f8552e7fefb4d1754ae Mon Oct 04 14:14:03 CDT 2010 Johannes Berg <johannes.berg@intel.com> genetlink: introduce pre_doit/post_doit hooks
Each family may have some amount of boilerplate
locking code that applies to most, or even all,
commands.
This allows a family to handle such things in
a more generic way, by allowing it to
a) include private flags in each operation
b) specify a pre_doit hook that is called,
before an operation's doit() callback and
may return an error directly,
c) specify a post_doit hook that can undo
locking or similar things done by pre_doit,
and finally
d) include two private pointers in each info
struct passed between all these operations
including doit(). (It's two because I'll
need two in nl80211 -- can be extended.)
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Acked-by: David S. Miller <davem@davemloft.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
|