Hello, On Mon, 29 Aug 2016 12:07:16 +0200, Stefan Roese wrote: > As you've probably already noticed, v2 of this patch with > COMPILE_TEST removed also did run into this linking problem - > for ARM64 in this case. So its perhaps best to provide this MBus > driver stub function. COMPILE_TEST could then be enabled again. Yes, I noticed. > What do you think? Should I post a separate patch to the MBus > driver (also attached)? Or should I squash it into v3 of this > XOR DMA driver patch (with COMPILE_TEST added gain)? Submitting as a separate patch is better IMO, it's touching a separate driver. Just submit both in the same patch series, the kbuild test robot will then only test building the XOR change with the MBus change applied. Thanks a lot! Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
