diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2016-10-27 15:49:12 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2016-10-27 15:49:12 -0700 |
commit | 9db4f36e82c2394c958d8e42a498fb664684bc22 (patch) | |
tree | 6b064b9f2b6c593639004c2a8a784a861dbca546 /mm/Kconfig | |
parent | 4e68af0b0694ac5f16d0c61a7682aa2d46348454 (diff) | |
download | linux-9db4f36e82c2394c958d8e42a498fb664684bc22.tar.bz2 |
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 'mm/Kconfig')
0 files changed, 0 insertions, 0 deletions