iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Richard Kuo <rkuo@codeaurora.org>
Cc: Christoph Hellwig <hch@lst.de>,
	linux-hexagon@vger.kernel.org, iommu@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] hexagon: remove the sync_single_for_cpu DMA operation
Date: Mon, 27 Aug 2018 10:41:31 +0200	[thread overview]
Message-ID: <20180827084131.GA21563@lst.de> (raw)
In-Reply-To: <20180808001927.GA20752@codeaurora.org>

Given that it didn't make 4.19-rc1, I'll pull this into the dma-mapping
tree first thing for 4.20 as I have some other changes that will go on
top of it.

  parent reply	other threads:[~2018-08-27  8:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 12:56 use the generic dma-noncoherent code for hexagon Christoph Hellwig
2018-07-19 12:56 ` [PATCH 1/3] hexagon: remove the sync_single_for_cpu DMA operation Christoph Hellwig
     [not found]   ` <20180719125635.824-2-hch-jcswGhMUV9g@public.gmane.org>
2018-07-25  3:29     ` Richard Kuo
     [not found]       ` <20180725032948.GG12771-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-07-25  4:39         ` Christoph Hellwig
2018-07-31 15:22           ` Christoph Hellwig
     [not found]             ` <20180731152229.GA956-jcswGhMUV9g@public.gmane.org>
2018-08-07  7:01               ` Christoph Hellwig
     [not found]                 ` <20180807070136.GA32634-jcswGhMUV9g@public.gmane.org>
2018-08-08  0:19                   ` Richard Kuo
2018-08-08  6:19                     ` Christoph Hellwig
2018-08-27  8:41                     ` Christoph Hellwig [this message]
2018-07-19 12:56 ` [PATCH 2/3] hexagon: implement the sync_sg_for_device " Christoph Hellwig
2018-07-19 12:56 ` [PATCH 3/3] hexagon: use generic dma_noncoherent_ops 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=20180827084131.GA21563@lst.de \
    --to=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkuo@codeaurora.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;
as well as URLs for NNTP newsgroup(s).