On Thu, Jul 19, 2018 at 06:02:28AM -0700, Christoph Hellwig wrote:
> Hi Openrisc maintainers,
>
> can you review these patches to switch openrisc to use the generic
> dma-noncoherent code? All the requirements are in mainline already
> and we've switched various architectures over to it already.
t; coherency bugs.
The below looks good. I am always happy to what looks like legacy copy & paste
cruft.
Acked-by: Stafford Horne
> Signed-off-by: Christoph Hellwig
> ---
> arch/openrisc/kernel/dma.c | 22 +-
> 1 file changed, 9 insertions(+), 13 deletio
On Mon, Feb 24, 2020 at 11:44:45AM -0800, Christoph Hellwig wrote:
> Switch openrisc to use the dma-direct allocator and just provide the
> hooks for setting memory uncached or cached.
>
> Signed-off-by: Christoph Hellwig
Reviewed-by: Stafford Horne
I also test booted this serie
On Mon, Feb 24, 2020 at 08:45:28PM +0100, Christoph Hellwig wrote:
> On Sat, Feb 22, 2020 at 07:14:47AM +0900, Stafford Horne wrote:
> > On Thu, Feb 20, 2020 at 09:01:39AM -0800, Christoph Hellwig wrote:
> > > Switch openrisc to use the dma-direct allocator and just provi
On Thu, Feb 20, 2020 at 09:01:39AM -0800, Christoph Hellwig wrote:
> Switch openrisc to use the dma-direct allocator and just provide the
> hooks for setting memory uncached or cached.
>
> Signed-off-by: Christoph Hellwig
Reviewed-by: Stafford Horne
Also, I test booted openrisc wi
00/kernel/setup.c| 8 +++-
> arch/nds32/kernel/setup.c| 8 ++--
> arch/openrisc/kernel/setup.c | 9 ++---
> 3 files changed, 7 insertions(+), 18 deletions(-)
Hi Mike,
For the openrisc part:
Acked-by: Stafford Horne
> --- a/arch/openrisc/kernel/setup.c
> +++ b/a
