All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Max Filippov <jcmvbkbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Chris Zankel <chris-YvXeqwSYzG2sTnJN9+BGXg@public.gmane.org>,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
	linux-xtensa-PjhNF2WwrV/0Sa2dR60CXw@public.gmane.org
Subject: Re: [PATCH] xtensa: use generic dma_noncoherent_ops
Date: Wed, 11 Jul 2018 20:00:40 +0200	[thread overview]
Message-ID: <20180711180040.GA4262@lst.de> (raw)
In-Reply-To: <CAMo8BfKzV6fhANk=ymsWFWoVtsYq3wXh559==rfjG2FimEC3+g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Wed, Jul 11, 2018 at 10:57:30AM -0700, Max Filippov wrote:
> >  config XTENSA
> >         def_bool y
> >         select ARCH_NO_COHERENT_DMA_MMAP if !MMU
> > +       select ARCH_HAS_SYNC_DMA_FOR_CPU
> > +       select ARCH_HAS_SYNC_DMA_FOR_DEVICE
> 
> This breaks alphabetical order of selects. Otherwise LGTM.
> Sorry for the delay.
> Acked-by: Max Filippov <jcmvbkbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> 
> Will you submit it further or should I take it into the xtensa tree?

Either way is fine with me, just let me know which way you prefer.

  parent reply	other threads:[~2018-07-11 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19  7:03 [PATCH] xtensa: use generic dma_noncoherent_ops Christoph Hellwig
     [not found] ` <20180619070316.26327-1-hch-jcswGhMUV9g@public.gmane.org>
2018-07-11 15:32   ` Christoph Hellwig
2018-07-11 17:57   ` Max Filippov
     [not found]     ` <CAMo8BfKzV6fhANk=ymsWFWoVtsYq3wXh559==rfjG2FimEC3+g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-07-11 18:00       ` Christoph Hellwig [this message]
     [not found]         ` <20180711180040.GA4262-jcswGhMUV9g@public.gmane.org>
2018-07-11 18:06           ` Max Filippov

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=20180711180040.GA4262@lst.de \
    --to=hch-jcswghmuv9g@public.gmane.org \
    --cc=chris-YvXeqwSYzG2sTnJN9+BGXg@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=jcmvbkbc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-xtensa-PjhNF2WwrV/0Sa2dR60CXw@public.gmane.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.