aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/conf.py
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2017-09-07 21:39:15 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2017-09-07 21:39:15 -0700
commit5969d1bb3082b41eba8fd2c826559abe38ccb6df (patch)
tree39f72fe44d2842ee29e89b0d23c61569fa7f725c /Documentation/conf.py
parentMerge tag 'scsi-misc' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi (diff)
parentRemove gperf usage from toolchain (diff)
downloadlinux-dev-5969d1bb3082b41eba8fd2c826559abe38ccb6df.tar.xz
linux-dev-5969d1bb3082b41eba8fd2c826559abe38ccb6df.zip
Merge branch 'gperf-removal'
Remove our use of 'gperf' for generating perfect hashes from some of our build tools. This removal was prompted by Masahiro Yamada sending out a patch that removes all our pre-generated files, and when I tested it, I noticed that the gperf version I have (3.1) apparently generates code that no longer works with out code-base because the function interfaces generated by gperf have changed. We really don't care that much, and the gperf people changed their interfaces in ways that makes it annoying to work with them. Tools that make it hard to use them should not be used, and the kernel is not at all interested in some autoconf mess. So remove the gperf dependency entirely. It turns out that if you ignore the pre-generated files, the use of gperf apparently saved us a whopping fifteen lines of code. It obviously wasn't worth it, considering that the pre-generated files are about 500 lines. I sent this out as a patch about three weeks ago, and got absolutely zero responses. So let's see if anybody notices now that I merge it. Because there might be serious bugs here, but it WorksForMe(tm). * gperf-removal: Remove gperf usage from toolchain
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions