diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2010-11-18 10:56:29 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2010-11-18 10:56:29 -0800 |
| commit | ed1d77b18c9f4ff06d5b42c65041aa55a1447053 (patch) | |
| tree | 9356285fc858fa6b60af7e99e827c129a696f6c6 /mm/memory.c | |
| parent | fb3ff69d1397ce4bd2441c87b1daea67cb945ac6 (diff) | |
| download | kernel_samsung_aries-ed1d77b18c9f4ff06d5b42c65041aa55a1447053.zip kernel_samsung_aries-ed1d77b18c9f4ff06d5b42c65041aa55a1447053.tar.gz kernel_samsung_aries-ed1d77b18c9f4ff06d5b42c65041aa55a1447053.tar.bz2 | |
hardirq.h: needs sched.h if using BKL
This really isn't the right thing to do, and strictly speaking we should
have the BKL depth count in the thread info right next to the preempt
count. The two really do go together.
However, since that would involve a patch to all architectures, and the
BKL is finally going away, it's simply not worth the effort to do the
RightThing(tm). Just re-instate the <linux/sched.h> include that we
used to get accidentally from the smp_lock.h one.
This is all fallout from the same old "BKL: remove extraneous #include
<smp_lock.h>" commit.
Reported-by: Ingo Molnar <mingo@elte.hu>
Tested-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/memory.c')
0 files changed, 0 insertions, 0 deletions