merge conflict and needs to be dealt with manually!
>>
>> So I haven't gotten the powerpc or microblaze pull requests yet, so
>> I'm not able to fix that part up yet.
>>
>> Intead, I'm cc'ing Michael Ellerman and Michal Simek to ask them to
>&g
ne that
> seems very straightfoward to convert.
>
I took at look at this series and tested it on kc705 and I can't see any
issue.
Patches applied.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel
ly get all
>> architectures over to the generic code, and microblaze is one that
>> seems very straightfoward to convert.
>
> Michal, any chance you could look over this series?
>
let me take a look.
M
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www
Hi Rob,
2018-09-05 21:37 GMT+02:00 Rob Herring :
> This series adds an iterator for cpu nodes and converts users over to use
> it or of_get_cpu_node in some cases. This allows us to remove the
> dependency on device_type property for cpu nodes though removing that
> from DTS files will have to wa
Hi,
On 19.7.2018 14:54, Christoph Hellwig wrote:
> Hi Michal,
>
> can you review these patches to switch microblaze to use the generic
> dma-noncoherent code? All the requirements are in mainline already
> and we've switched various architectures over to it already.
>
I can't see any issue wit
