From: Rich Felker <dalias@libc.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Jacopo Mondi <jacopo+renesas@jmondi.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
linux-sh@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: use the generic dma-noncoherent code for sh V3
Date: Wed, 1 Aug 2018 22:09:06 -0400 [thread overview]
Message-ID: <20180802020906.GK1392@brightrain.aerifal.cx> (raw)
In-Reply-To: <20180731072413.GA22837@lst.de>
On Tue, Jul 31, 2018 at 09:24:13AM +0200, Christoph Hellwig wrote:
> On Tue, Jul 31, 2018 at 03:06:13PM +0900, Yoshinori Sato wrote:
> > On Wed, 25 Jul 2018 18:40:38 +0900,
> > Christoph Hellwig wrote:
> > >
> > > Hi all,
> > >
> > > can you review these patches to switch sh to use the generic
> > > dma-noncoherent code? All the requirements are in mainline already
> > > and we've switched various architectures over to it already.
> > >
> > > Changes since V2:
> > > - drop a now obsolete export
> > >
> > > Changes since V1:
> > > - fixed two stupid compile errors and verified them using a local
> > > cross toolchain instead of the 0day buildbot
> >
> > Acked-by: Yoshinori Sato <ysato@users.sourceforge.jp>
>
> Do you want to pull this in through the sh tree? If not I'd be happy
> to take it through the dma mapping tree.
Usually I send the pull requests for sh tree, and I'm trying to figure
out which patches are okay to merge and prepare one now, but if you're
happy to take it through the dma mapping tree go ahead, and I'll focus
on other sh stuff that needs attention.
Rich
next prev parent reply other threads:[~2018-08-02 2:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 9:40 Christoph Hellwig
2018-07-25 9:40 ` [PATCH 1/5] sh: simplify get_arch_dma_ops Christoph Hellwig
2018-07-25 9:40 ` [PATCH 2/5] sh: introduce a sh_cacheop_vaddr helper Christoph Hellwig
2018-07-25 9:40 ` [PATCH 3/5] sh: use dma_direct_ops for the CONFIG_DMA_COHERENT case Christoph Hellwig
2018-07-25 9:40 ` [PATCH 4/5] sh: split arch/sh/mm/consistent.c Christoph Hellwig
2018-07-25 9:40 ` [PATCH 5/5] sh: use generic dma_noncoherent_ops Christoph Hellwig
2018-07-31 6:06 ` use the generic dma-noncoherent code for sh V3 Yoshinori Sato
2018-07-31 7:24 ` Christoph Hellwig
2018-08-02 2:09 ` Rich Felker [this message]
2018-08-02 7:15 ` Christoph Hellwig
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=20180802020906.GK1392@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=jacopo+renesas@jmondi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®