| commit | 1014eb6ec95b18f890101e99385f05539c0c2f01 | |
| author | Jean Tourrilhes <jt@hpl.hp.com> | |
| Tue, 24 Nov 2009 18:47:08 +0000 (24 10:47 -0800) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Fri, 4 Dec 2009 18:30:39 +0000 (4 13:30 -0500) | ||
| tree | 6ef0eb2946e197b93fd317993fc1fc61aadd27e0 | treesnapshot (tar.gz zip) |
| parent | 316a4d966cae3c2dec83ebb1ee1a3515f97b30ff | commitdiff |
WE: Fix set events not propagated
I've just noticed that some events are no longer propagated
for some wireless drivers. Basically, SET request with a extra payload
for driver without commit handler. The fix is pretty simple, see
attached.
Actually, a few lines below this line, you will see that the
event generation for simple SET (iwpoint-less ?) is done properly,
and this other event generation does not need fixing.
Signed-off-by: Jean Tourrilhes <jt@hpl.hp.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
I've just noticed that some events are no longer propagated
for some wireless drivers. Basically, SET request with a extra payload
for driver without commit handler. The fix is pretty simple, see
attached.
Actually, a few lines below this line, you will see that the
event generation for simple SET (iwpoint-less ?) is done properly,
and this other event generation does not need fixing.
Signed-off-by: Jean Tourrilhes <jt@hpl.hp.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| net/wireless/wext-core.c | diffblobblamehistory |