iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] dma-mapping fixes for 5.8
Date: Sat, 27 Jun 2020 09:49:02 +0200	[thread overview]
Message-ID: <20200627074902.GA2447682@infradead.org> (raw)

The following changes since commit dbed452a078d56bc7f1abecc3edd6a75e8e4484e:

  dma-pool: decouple DMA_REMAP from DMA_COHERENT_POOL (2020-06-15 08:35:30 +0200)

are available in the Git repository at:

  git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.8-4

for you to fetch changes up to 8e36baf97b252cdcafa53589e8227cbb1e85f0b0:

  dma-remap: align the size in dma_common_*_remap() (2020-06-23 14:14:41 +0200)

----------------------------------------------------------------
dma-mapping fixes for 5.8:

 - fix dma coherent mmap in nommu (me)
 - more AMD SEV fallout (David Rientjes, me)
 - fix alignment in dma_common_*_remap (Eric Auger)

----------------------------------------------------------------
Christoph Hellwig (3):
      dma-direct: re-enable mmap for !CONFIG_MMU
      dma-direct: mark __dma_direct_alloc_pages static
      dma-mapping: DMA_COHERENT_POOL should select GENERIC_ALLOCATOR

David Rientjes (4):
      dma-direct: always align allocation size in dma_direct_alloc_pages()
      dma-direct: re-encrypt memory if dma_direct_alloc_pages() fails
      dma-direct: check return value when encrypting or decrypting memory
      dma-direct: add missing set_memory_decrypted() for coherent mapping

Eric Auger (1):
      dma-remap: align the size in dma_common_*_remap()

 include/linux/dma-direct.h |  2 --
 kernel/dma/Kconfig         |  3 ++-
 kernel/dma/direct.c        | 59 ++++++++++++++++++++++++++--------------------
 kernel/dma/remap.c         |  5 ++--
 4 files changed, 39 insertions(+), 30 deletions(-)
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

             reply	other threads:[~2020-06-27  7:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-27  7:49 Christoph Hellwig [this message]
2020-06-27 20:25 ` [GIT PULL] dma-mapping fixes for 5.8 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2020-07-19  7:39 Christoph Hellwig
2020-07-19 20:00 ` pr-tracker-bot
2020-07-10 15:45 Christoph Hellwig
2020-07-10 16:55 ` pr-tracker-bot
2020-06-17  7:27 Christoph Hellwig
2020-06-17 18:35 ` pr-tracker-bot

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=20200627074902.GA2447682@infradead.org \
    --to=hch@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).