summaryrefslogtreecommitdiffstats
path: root/lib/locking-selftest-wsem.h
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2016-10-28 00:49:12 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2016-10-28 00:49:12 +0200
commit9db4f36e82c2394c958d8e42a498fb664684bc22 (patch)
tree6b064b9f2b6c593639004c2a8a784a861dbca546 /lib/locking-selftest-wsem.h
parentMerge branch 'i2c/for-current' of git://git.kernel.org/pub/scm/linux/kernel/g... (diff)
downloadlinux-9db4f36e82c2394c958d8e42a498fb664684bc22.tar.xz
linux-9db4f36e82c2394c958d8e42a498fb664684bc22.zip
mm: remove unused variable in memory hotplug
When I removed the per-zone bitlock hashed waitqueues in commit 9dcb8b685fc3 ("mm: remove per-zone hashtable of bitlock waitqueues"), I removed all the magic hotplug memory initialization of said waitqueues too. But when I actually _tested_ the resulting build, I stupidly assumed that "allmodconfig" would enable memory hotplug. And it doesn't, because it enables KASAN instead, which then disables hotplug memory support. As a result, my build test of the per-zone waitqueues was totally broken, and I didn't notice that the compiler warns about the now unused iterator variable 'i'. I guess I should be happy that that seems to be the worst breakage from my clearly horribly failed test coverage. Reported-by: Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'lib/locking-selftest-wsem.h')
0 files changed, 0 insertions, 0 deletions