Re: use the generic dma-noncoherent code for microblaze

From: Michal Simek
Date: Fri Jul 20 2018 - 08:34:01 EST

Next message: Greg Kroah-Hartman: "[PATCH 4.14 26/92] net/mlx5e: Dont attempt to dereference the ppriv struct if not being eswitch manager"
Previous message: Greg Kroah-Hartman: "[PATCH 4.14 31/92] net/mlx5: Fix wrong size allocation for QoS ETC TC regitster"
In reply to: Christoph Hellwig: "[PATCH 1/2] microblaze: use generic dma_noncoherent_ops"
Next in thread: Christoph Hellwig: "Re: use the generic dma-noncoherent code for microblaze"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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 with them.
Both applied to next.

Thanks,
Michal

Next message: Greg Kroah-Hartman: "[PATCH 4.14 26/92] net/mlx5e: Dont attempt to dereference the ppriv struct if not being eswitch manager"
Previous message: Greg Kroah-Hartman: "[PATCH 4.14 31/92] net/mlx5: Fix wrong size allocation for QoS ETC TC regitster"
In reply to: Christoph Hellwig: "[PATCH 1/2] microblaze: use generic dma_noncoherent_ops"
Next in thread: Christoph Hellwig: "Re: use the generic dma-noncoherent code for microblaze"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]