Linux IOMMU Development
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Cc: Corentin Labbe
	<clabbe.montjoie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Subject: various DMA mapping fixes for 4.21-rc1
Date: Wed,  2 Jan 2019 09:33:14 +0100	[thread overview]
Message-ID: <20190102083319.12374-1-hch@lst.de> (raw)

Hi all,

this series fixes up some fallout from the changes in this merge window.
Patch 1 ensures dma-debug works correctly with the merge map_page /
map_single implementation, patch 4 makes sure the DMA API calls
are properly stubbed out for COMPILE_TEST builds on UML.  Patches 2 and
3 make patch 4 a little simpler, and patch 5 removes various exports
no needed now that we moved a lot of functionality out of line.

             reply	other threads:[~2019-01-02  8:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02  8:33 Christoph Hellwig [this message]
     [not found] ` <20190102083319.12374-1-hch-jcswGhMUV9g@public.gmane.org>
2019-01-02  8:33   ` [PATCH 1/5] dma-mapping: implement dma_map_single_attrs using dma_map_page_attrs Christoph Hellwig
2019-01-02  8:33   ` [PATCH 2/5] dma-mapping: implement dmam_alloc_coherent using dmam_alloc_attrs Christoph Hellwig
2019-01-02  8:33   ` [PATCH 3/5] dma-mapping: remove dmam_{declare, release}_coherent_memory Christoph Hellwig
2019-01-02  8:33   ` [PATCH 4/5] dma-mapping: properly stub out the DMA API for !CONFIG_HAS_DMA Christoph Hellwig
2019-01-02  8:33   ` [PATCH 5/5] dma-mapping: remove a few unused exports 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=20190102083319.12374-1-hch@lst.de \
    --to=hch-jcswghmuv9g@public.gmane.org \
    --cc=clabbe.montjoie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=robin.murphy-5wv7dgnIgG8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox