https://bugs.kde.org/show_bug.cgi?id=408004
--- Comment #33 from awf_ul <awf...@charter.net> ---
Below is the result of the second bisect (see bisect log in attachment "Second
bisect; failure repeatable and solid")
55897af63091ebc2c3f239c6a6666f748113ac50 is the first bad commit
commit 55897af63091ebc2c3f239c6a6666f748113ac50
Author: Christoph Hellwig <h...@lst.de>
Date: Mon Dec 3 11:43:54 2018 +0100
dma-direct: merge swiotlb_dma_ops into the dma_direct code
While the dma-direct code is (relatively) clean and simple we actually
have to use the swiotlb ops for the mapping on many architectures due
to devices with addressing limits. Instead of keeping two
implementations around this commit allows the dma-direct
implementation to call the swiotlb bounce buffering functions and
thus share the guts of the mapping implementation. This also
simplified the dma-mapping setup on a few architectures where we
don't have to differenciate which implementation to use.
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 e9b0807231777e3da732cb3f744a8867f3128f90
95962d177078f04ae1bd66f560c87a9eed9d0f0e M arch
:040000 040000 e7a90740563e49061bb6baf6413e9de37a919820
b537630e5cf02def1bcfac744cd06da0f8201ff8 M include
:040000 040000 4698daf585ffbc830cfda58e8a2e8390f66b4cf9
a942b6a22ca5f49aaef13490a03e4589766fd497 M kernel
--
You are receiving this mail because:
You are watching all bug changes.
