https://bugs.kde.org/show_bug.cgi?id=408004
--- Comment #25 from awf_ul <awf...@charter.net> ---
Did bisect, checking each kernel compilation along the way; the failing commit
is here:
3731c3d4774e38b9d91c01943e1e6a243c1776be is the first bad commit
commit 3731c3d4774e38b9d91c01943e1e6a243c1776be
Author: Christoph Hellwig <h...@lst.de>
Date: Thu Dec 6 12:50:26 2018 -0800
dma-mapping: always build the direct mapping code
All architectures except for sparc64 use the dma-direct code in some
form, and even for sparc64 we had the discussion of a direct mapping
mode a while ago. In preparation for directly calling the direct
mapping code don't bother having it optionally but always build the
code in. This is a minor hardship for some powerpc and arm configs
that don't pull it in yet (although they should in a relase ot two),
and sparc64 which currently doesn't need it at all, but it will
reduce the ifdef mess we'd otherwise need significantly.
Signed-off-by: Christoph Hellwig <h...@lst.de>
Acked-by: Jesper Dangaard Brouer <bro...@redhat.com>
Tested-by: Jesper Dangaard Brouer <bro...@redhat.com>
Tested-by: Tony Luck <tony.l...@intel.com>
:040000 040000 639c86795e7435f7dde3bf8a48f183f932c08e16
ab40fc2f930f14428513fca3
739ef28b7b9cefd1 M arch
:040000 040000 28ddf6fbe5648c7655ac4eed39116e451c996885
e5c852697674caada8c62f1936646e0155d90061 M kernel
--
You are receiving this mail because:
You are watching all bug changes.
