diff options
author | Johannes Berg <johannes@sipsolutions.net> | 2009-07-05 14:51:06 +0200 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2009-07-10 15:02:29 -0400 |
commit | 1be491fca12ff599c37ceaf7e9042ebee9f0068e (patch) | |
tree | 96033bde1ed8561201c42574ec716f7cfd033697 /net/rfkill/rfkill.h | |
parent | 3355443ad7601991affa5992b0d53870335af765 (diff) | |
download | linux-3.10-1be491fca12ff599c37ceaf7e9042ebee9f0068e.tar.gz linux-3.10-1be491fca12ff599c37ceaf7e9042ebee9f0068e.tar.bz2 linux-3.10-1be491fca12ff599c37ceaf7e9042ebee9f0068e.zip |
rfkill: prep for rfkill API changes
We've designed the /dev/rfkill API in a way that we
can increase the event struct by adding members at
the end, should it become necessary. To validate the
events, userspace and the kernel need to have the
proper event size to check for -- when reading from
the other end they need to verify that it's at least
version 1 of the event API, with the current struct
size, so define a constant for that and make the
code a little more 'future proof'.
Not that I expect that we'll have to change the event
size any time soon, but it's better to write the code
in a way that lends itself to extending.
Due to the current size of the event struct, the code
is currently equivalent, but should the event struct
ever need to be increased the new code might not need
changing.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'net/rfkill/rfkill.h')
0 files changed, 0 insertions, 0 deletions