From: Christoph Hellwig <hch@lst.de>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: linux-xtensa@linux-xtensa.org, Chris Zankel <chris@zankel.net>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xtensa: implement arch_dma_coherent_to_pfn
Date: Wed, 16 Oct 2019 09:08:27 +0200 [thread overview]
Message-ID: <20191016070827.GA23051@lst.de> (raw)
In-Reply-To: <20191015212526.1775-1-jcmvbkbc@gmail.com>
On Tue, Oct 15, 2019 at 02:25:26PM -0700, Max Filippov wrote:
> Add trivial implementation for arch_dma_coherent_to_pfn.
> This change enables communication with PCI ALSA devices through mmapped
> buffers.
This looks fine, although I'd much rather convert xtensa to the
generic DMA remap / uncached segment support.
Do you want this fix for 5.4? If so please queue it up ASAP so that
I can do the proper thing for 5.5. If you don't need it that urgent
I'd rather go straight to the generic code.
next prev parent reply other threads:[~2019-10-16 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 21:25 [PATCH] xtensa: implement arch_dma_coherent_to_pfn Max Filippov
2019-10-16 7:08 ` Christoph Hellwig [this message]
2019-10-16 7:40 ` 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=20191016070827.GA23051@lst.de \
--to=hch@lst.de \
--cc=chris@zankel.net \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox