summaryrefslogtreecommitdiffstats
path: root/net/rfkill
diff options
context:
space:
mode:
authorPaul Gortmaker <paul.gortmaker@windriver.com>2012-01-22 11:23:42 -0500
committerPaul Gortmaker <paul.gortmaker@windriver.com>2012-03-11 14:27:37 -0400
commit51990e825431089747f8896244b5c17d3a6423f1 (patch)
tree5c1ef975ab55734a45444b629855a51f09775b93 /net/rfkill
parentdcd6c92267155e70a94b3927bce681ce74b80d1f (diff)
downloadlinux-stable-51990e825431089747f8896244b5c17d3a6423f1.tar.gz
linux-stable-51990e825431089747f8896244b5c17d3a6423f1.tar.bz2
linux-stable-51990e825431089747f8896244b5c17d3a6423f1.zip
device.h: cleanup users outside of linux/include (C files)
For files that are actively using linux/device.h, make sure that they call it out. This will allow us to clean up some of the implicit uses of linux/device.h within include/* without introducing build regressions. Yes, this was created by "cheating" -- i.e. the headers were cleaned up, and then the fallout was found and fixed, and then the two commits were reordered. This ensures we don't introduce build regressions into the git history. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Diffstat (limited to 'net/rfkill')
-rw-r--r--net/rfkill/core.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/net/rfkill/core.c b/net/rfkill/core.c
index 354760ebbbd2..f974961754ca 100644
--- a/net/rfkill/core.c
+++ b/net/rfkill/core.c
@@ -29,6 +29,7 @@
#include <linux/rfkill.h>
#include <linux/sched.h>
#include <linux/spinlock.h>
+#include <linux/device.h>
#include <linux/miscdevice.h>
#include <linux/wait.h>
#include <linux/poll.h>