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 4.17-rc3
Date: Wed, 25 Apr 2018 07:22:25 +0200 [thread overview]
Message-ID: <20180425052225.GA2350@infradead.org> (raw)
The following changes since commit 6d08b06e67cd117f6992c46611dfb4ce267cd71e:
Linux 4.17-rc2 (2018-04-22 19:20:09 -0700)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-4.17-3
for you to fetch changes up to 60695be2bb6b0623f8e53bd9949d582a83c6d44a:
dma-mapping: postpone cpu addr translation on mmap (2018-04-23 14:44:24 +0200)
----------------------------------------------------------------
A few small dma-mapping fixes for Linux 4.17-rc3:
- don't loop to try GFP_DMA allocations if ZONE_DMA is not actually
enabled (regression in 4.16)
- don't try to do virt_to_page before we know we actuall have a
valid page in dma_common_mmap
- a comment fixup related to the above fix
----------------------------------------------------------------
Jacopo Mondi (1):
dma-mapping: postpone cpu addr translation on mmap
Robin Murphy (1):
dma-coherent: clarify dma_mmap_from_dev_coherent documentation
Takashi Iwai (1):
dma-direct: don't retry allocation for no-op GFP_DMA
drivers/base/dma-coherent.c | 5 +++--
drivers/base/dma-mapping.c | 6 ++----
lib/dma-direct.c | 3 ++-
3 files changed, 7 insertions(+), 7 deletions(-)
next reply other threads:[~2018-04-25 5:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 5:22 Christoph Hellwig [this message]
2018-04-25 6:54 ` [GIT PULL] dma mapping fixes for 4.17-rc3 David Rientjes
2018-04-25 6:59 ` Christoph Hellwig
2018-04-25 7:09 ` David Rientjes
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=20180425052225.GA2350@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