Hey Arnd, On Fri, Sep 28, 2018 at 9:19 PM Arnd Bergmann <a...@arndb.de> wrote: > You can probably work around it by enabling ARCH_HIGHBANK, > which is a minimal platform with no other requirements, so it > should only add a few milliseconds to the build.
Nice hack, thanks for the suggestion. Committed here: https://git.kernel.org/pub/scm/linux/kernel/git/zx2c4/WireGuard.git/commit/?id=56ff2eb9480e6c691a5b8d8ff1fa01090df61e1d > Another option would be to do the testing on top of linux-next, > which should have your fix starting on Monday. Testing on > linux-next carries a higher risk of running into unrelated > regressions, but also lets you find out about conflicts with > other patches early on. I do actually test on linux-next (and tons of other kernels too), but I like to have things working for at least the latest mainline. Jason
