aboutsummaryrefslogtreecommitdiff
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorGravatar Linus Torvalds <torvalds@linux-foundation.org> 2024-04-12 10:05:10 -0700
committerGravatar Linus Torvalds <torvalds@linux-foundation.org> 2024-04-12 10:05:10 -0700
commitd5cf50dafc9dd5faa1e61e7021e3496ddf7fd61e (patch)
treebe73935c7bb5970c98f12511fa9e2fa89d2a896f /MAINTAINERS
parentMerge tag 'trace-v6.9-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/t... (diff)
downloadlinux-d5cf50dafc9dd5faa1e61e7021e3496ddf7fd61e.tar.gz
linux-d5cf50dafc9dd5faa1e61e7021e3496ddf7fd61e.tar.bz2
linux-d5cf50dafc9dd5faa1e61e7021e3496ddf7fd61e.zip
Kconfig: add some hidden tabs on purpose
Commit d96c36004e31 ("tracing: Fix FTRACE_RECORD_RECURSION_SIZE Kconfig entry") removed a hidden tab because it apparently showed breakage in some third-party kernel config parsing tool. It wasn't clear what tool it was, but let's make sure it gets fixed. Because if you can't parse tabs as whitespace, you should not be parsing the kernel Kconfig files. In fact, let's make such breakage more obvious than some esoteric ftrace record size option. If you can't parse tabs, you can't have page sizes. Yes, tab-vs-space confusion is sadly a traditional Unix thing, and 'make' is famous for being broken in this regard. But no, that does not mean that it's ok. I'd add more random tabs to our Kconfig files, but I don't want to make things uglier than necessary. But it *might* bbe necessary if it turns out we see more of this kind of silly tooling. Fixes: d96c36004e31 ("tracing: Fix FTRACE_RECORD_RECURSION_SIZE Kconfig entry") Link: https://lore.kernel.org/lkml/CAHk-=wj-hLLN_t_m5OL4dXLaxvXKy_axuoJYXif7iczbfgAevQ@mail.gmail.com/ Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions