diff options
author | Dave Hansen <dave@linux.vnet.ibm.com> | 2013-07-01 13:04:43 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2013-07-04 11:25:39 -0700 |
commit | 0610c8a8a258e869a542e5fdb964c6816336559e (patch) | |
tree | d70e7aba355ec74c4310ac5f4cc57a8f713954ea /sound | |
parent | d1a1dc0be866219f7a613c6368c6a036b8eefe03 (diff) | |
download | op-kernel-dev-0610c8a8a258e869a542e5fdb964c6816336559e.zip op-kernel-dev-0610c8a8a258e869a542e5fdb964c6816336559e.tar.gz |
order memory debugging Kconfig options
Original posting:
http://lkml.kernel.org/r/20121214184203.37E6C724@kernel.stglabs.ibm.com
There are a *LOT* of memory debugging options. They are just scattered
all over the "Kernel Hacking" menu. Sure, "memory debugging" is a very
vague term and it's going to be hard to make absolute rules about what
goes in here, but this has to be better than what we had before.
This does, however, leave out the architecture-specific memory
debugging options (like x86's DEBUG_SET_MODULE_RONX). There would need
to be some substantial changes to move those in here. Kconfig can not
easily mix arch-specific and generic options together: it really
requires a file per-architecture, and I think having an
arch/foo/Kconfig.debug-memory might be taking things a bit too far
Signed-off-by: Dave Hansen <dave@linux.vnet.ibm.com>
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'sound')
0 files changed, 0 insertions, 0 deletions