All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] powerpc: use the generic dma coherent remap allocator
Date: Wed, 28 Aug 2019 16:25:46 +0200	[thread overview]
Message-ID: <20190828142546.GA29960@lst.de> (raw)
In-Reply-To: <87blw9v2ge.fsf@mpe.ellerman.id.au>

On Wed, Aug 28, 2019 at 11:34:09PM +1000, Michael Ellerman wrote:
> Christoph Hellwig <hch@lst.de> writes:
> > Michael,
> >
> > do oyu plan to pick this up?  Otherwise I'd love to pick it up through
> > the dma-mapping tree as that would avoid one trivial conflict with
> > another pending patch.
> 
> It conflicts a bit with the ioremap changes I already have in next.
> 
> And it would be good for it to get some testing on my machines here. So
> I guess I'd rather it went via the powerpc tree?

Sure, feel free to queue it up through the ppc tree.  I am about to
queue up a patch to move the dma_atomic_pool_init call to common code,
so as linux-next / Linus fixup we'll have to eventually remove
atomic_pool_init() again.

  reply	other threads:[~2019-08-28 14:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14 13:22 use the generic DMA direct remap code on powerpc Christoph Hellwig
2019-08-14 13:22 ` [PATCH] powerpc: use the generic dma coherent remap allocator Christoph Hellwig
2019-08-14 14:20   ` Christophe Leroy
2019-08-14 14:23     ` Christoph Hellwig
2019-08-14 14:21   ` Christophe Leroy
2019-08-28  6:10   ` Christoph Hellwig
2019-08-28 13:34     ` Michael Ellerman
2019-08-28 14:25       ` Christoph Hellwig [this message]
2019-08-29  9:42         ` Michael Ellerman
2019-09-02  3:29   ` Michael Ellerman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190828142546.GA29960@lst.de \
    --to=hch@lst.de \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.