/linux/net/mac80211/ |
H A D | mesh.h | diff f5ea9120be2e5d5c846243416cfdce01d02f5836 Fri Aug 07 16:17:38 CEST 2009 Johannes Berg <johannes@sipsolutions.net> nl80211: add generation number to all dumps
In order for userspace to be able to figure out whether it obtained a consistent snapshot of data or not when using netlink dumps, we need to have a generation number in each dump message that indicates whether the list has changed or not -- its value is arbitrary.
This patch adds such a number to all dumps, this needs some mac80211 involvement to keep track of a generation number to start with when adding/removing mesh paths or stations.
The wiphy and netdev lists can be fully handled within cfg80211, of course, but generation numbers need to be stored there as well.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | mesh_pathtbl.c | diff f5ea9120be2e5d5c846243416cfdce01d02f5836 Fri Aug 07 16:17:38 CEST 2009 Johannes Berg <johannes@sipsolutions.net> nl80211: add generation number to all dumps
In order for userspace to be able to figure out whether it obtained a consistent snapshot of data or not when using netlink dumps, we need to have a generation number in each dump message that indicates whether the list has changed or not -- its value is arbitrary.
This patch adds such a number to all dumps, this needs some mac80211 involvement to keep track of a generation number to start with when adding/removing mesh paths or stations.
The wiphy and netdev lists can be fully handled within cfg80211, of course, but generation numbers need to be stored there as well.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | sta_info.c | diff f5ea9120be2e5d5c846243416cfdce01d02f5836 Fri Aug 07 16:17:38 CEST 2009 Johannes Berg <johannes@sipsolutions.net> nl80211: add generation number to all dumps
In order for userspace to be able to figure out whether it obtained a consistent snapshot of data or not when using netlink dumps, we need to have a generation number in each dump message that indicates whether the list has changed or not -- its value is arbitrary.
This patch adds such a number to all dumps, this needs some mac80211 involvement to keep track of a generation number to start with when adding/removing mesh paths or stations.
The wiphy and netdev lists can be fully handled within cfg80211, of course, but generation numbers need to be stored there as well.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | ieee80211_i.h | diff f5ea9120be2e5d5c846243416cfdce01d02f5836 Fri Aug 07 16:17:38 CEST 2009 Johannes Berg <johannes@sipsolutions.net> nl80211: add generation number to all dumps
In order for userspace to be able to figure out whether it obtained a consistent snapshot of data or not when using netlink dumps, we need to have a generation number in each dump message that indicates whether the list has changed or not -- its value is arbitrary.
This patch adds such a number to all dumps, this needs some mac80211 involvement to keep track of a generation number to start with when adding/removing mesh paths or stations.
The wiphy and netdev lists can be fully handled within cfg80211, of course, but generation numbers need to be stored there as well.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | cfg.c | diff f5ea9120be2e5d5c846243416cfdce01d02f5836 Fri Aug 07 16:17:38 CEST 2009 Johannes Berg <johannes@sipsolutions.net> nl80211: add generation number to all dumps
In order for userspace to be able to figure out whether it obtained a consistent snapshot of data or not when using netlink dumps, we need to have a generation number in each dump message that indicates whether the list has changed or not -- its value is arbitrary.
This patch adds such a number to all dumps, this needs some mac80211 involvement to keep track of a generation number to start with when adding/removing mesh paths or stations.
The wiphy and netdev lists can be fully handled within cfg80211, of course, but generation numbers need to be stored there as well.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
/linux/net/wireless/ |
H A D | core.h | diff f5ea9120be2e5d5c846243416cfdce01d02f5836 Fri Aug 07 16:17:38 CEST 2009 Johannes Berg <johannes@sipsolutions.net> nl80211: add generation number to all dumps
In order for userspace to be able to figure out whether it obtained a consistent snapshot of data or not when using netlink dumps, we need to have a generation number in each dump message that indicates whether the list has changed or not -- its value is arbitrary.
This patch adds such a number to all dumps, this needs some mac80211 involvement to keep track of a generation number to start with when adding/removing mesh paths or stations.
The wiphy and netdev lists can be fully handled within cfg80211, of course, but generation numbers need to be stored there as well.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | scan.c | diff f5ea9120be2e5d5c846243416cfdce01d02f5836 Fri Aug 07 16:17:38 CEST 2009 Johannes Berg <johannes@sipsolutions.net> nl80211: add generation number to all dumps
In order for userspace to be able to figure out whether it obtained a consistent snapshot of data or not when using netlink dumps, we need to have a generation number in each dump message that indicates whether the list has changed or not -- its value is arbitrary.
This patch adds such a number to all dumps, this needs some mac80211 involvement to keep track of a generation number to start with when adding/removing mesh paths or stations.
The wiphy and netdev lists can be fully handled within cfg80211, of course, but generation numbers need to be stored there as well.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | core.c | diff f5ea9120be2e5d5c846243416cfdce01d02f5836 Fri Aug 07 16:17:38 CEST 2009 Johannes Berg <johannes@sipsolutions.net> nl80211: add generation number to all dumps
In order for userspace to be able to figure out whether it obtained a consistent snapshot of data or not when using netlink dumps, we need to have a generation number in each dump message that indicates whether the list has changed or not -- its value is arbitrary.
This patch adds such a number to all dumps, this needs some mac80211 involvement to keep track of a generation number to start with when adding/removing mesh paths or stations.
The wiphy and netdev lists can be fully handled within cfg80211, of course, but generation numbers need to be stored there as well.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
H A D | nl80211.c | diff f5ea9120be2e5d5c846243416cfdce01d02f5836 Fri Aug 07 16:17:38 CEST 2009 Johannes Berg <johannes@sipsolutions.net> nl80211: add generation number to all dumps
In order for userspace to be able to figure out whether it obtained a consistent snapshot of data or not when using netlink dumps, we need to have a generation number in each dump message that indicates whether the list has changed or not -- its value is arbitrary.
This patch adds such a number to all dumps, this needs some mac80211 involvement to keep track of a generation number to start with when adding/removing mesh paths or stations.
The wiphy and netdev lists can be fully handled within cfg80211, of course, but generation numbers need to be stored there as well.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|
/linux/include/net/ |
H A D | cfg80211.h | diff f5ea9120be2e5d5c846243416cfdce01d02f5836 Fri Aug 07 16:17:38 CEST 2009 Johannes Berg <johannes@sipsolutions.net> nl80211: add generation number to all dumps
In order for userspace to be able to figure out whether it obtained a consistent snapshot of data or not when using netlink dumps, we need to have a generation number in each dump message that indicates whether the list has changed or not -- its value is arbitrary.
This patch adds such a number to all dumps, this needs some mac80211 involvement to keep track of a generation number to start with when adding/removing mesh paths or stations.
The wiphy and netdev lists can be fully handled within cfg80211, of course, but generation numbers need to be stored there as well.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net> Signed-off-by: John W. Linville <linville@tuxdriver.com>
|