wext: remove seq_start/stop sparse annotations
authorJohannes Berg <johannes@sipsolutions.net>
Tue, 12 May 2009 06:36:43 +0000 (08:36 +0200)
committerJohn W. Linville <linville@tuxdriver.com>
Wed, 13 May 2009 19:44:40 +0000 (15:44 -0400)
Even though they are true, they cause sparse to complain
because it doesn't see the __acquires(dev_base_lock) on
dev_seq_start() because it is only added to the function
in net/core/dev.c, not the header file. To keep track of
the nesting correctly we should probably annotate those
functions publically, but for now let's just remove the
annotation I added to wext.

Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
net/wireless/wext.c

index dc5b47e84a3d76ce69254e4c88269ebc78d66785..d3bbef70cc7c3624882460569197b10c644c331a 100644 (file)
@@ -650,14 +650,12 @@ static int wireless_seq_show(struct seq_file *seq, void *v)
 }
 
 static void *wireless_dev_seq_start(struct seq_file *seq, loff_t *pos)
-       __acquires(dev_base_lock)
 {
        rtnl_lock();
        return dev_seq_start(seq, pos);
 }
 
 static void wireless_dev_seq_stop(struct seq_file *seq, void *v)
-       __releases(dev_base_lock)
 {
        dev_seq_stop(seq, v);
        rtnl_unlock();