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 updates for 5.2
Date: Thu, 9 May 2019 09:16:34 +0200 [thread overview]
Message-ID: <20190509071634.GA604@infradead.org> (raw)
Hi Linus,
a pretty small DMA mapping updates for this merge window below:
The following changes since commit 15ade5d2e7775667cf191cf2f94327a4889f8b9d:
Linux 5.1-rc4 (2019-04-07 14:09:59 -1000)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.2
for you to fetch changes up to 13bf5ced93775ffccb53527a9d862e023a9daa03:
dma-mapping: add a Kconfig symbol to indicate arch_dma_prep_coherent presence (2019-05-06 15:04:40 +0200)
----------------------------------------------------------------
DMA mapping updates for 5.2
- remove the already broken support for NULL dev arguments to the
DMA API calls
- Kconfig tidyups
----------------------------------------------------------------
Christoph Hellwig (8):
parport_ip32: pass struct device to DMA API functions
da8xx-fb: pass struct device to DMA API functions
gbefb: switch to managed version of the DMA allocator
pxa3xx-gcu: pass struct device to dma_mmap_coherent
arm: use a dummy struct device for ISA DMA use of the DMA API
dma-mapping: remove leftover NULL device support
x86/dma: Remove the x86_dma_fallback_dev hack
dma-mapping: add a Kconfig symbol to indicate arch_dma_prep_coherent presence
Clément Leger (1):
dma: select GENERIC_ALLOCATOR for DMA_REMAP
Dan Carpenter (1):
dma-mapping: remove an unnecessary NULL check
Documentation/DMA-API-HOWTO.txt | 13 ++++++-------
arch/arm/kernel/dma-isa.c | 8 +++++++-
arch/arm/mach-rpc/dma.c | 8 +++++++-
arch/arm64/Kconfig | 1 +
arch/csky/Kconfig | 1 +
arch/x86/include/asm/dma-mapping.h | 10 ----------
arch/x86/kernel/amd_gart_64.c | 6 ------
arch/x86/kernel/pci-dma.c | 20 --------------------
drivers/parport/parport_ip32.c | 18 ++++++++++--------
drivers/video/fbdev/da8xx-fb.c | 13 +++++++------
drivers/video/fbdev/gbefb.c | 24 ++++++++----------------
drivers/video/fbdev/pxa3xx-gcu.c | 4 +++-
include/linux/dma-mapping.h | 6 +++---
include/linux/dma-noncoherent.h | 6 ++++++
kernel/dma/Kconfig | 4 ++++
kernel/dma/direct.c | 2 +-
kernel/dma/mapping.c | 9 +--------
17 files changed, 65 insertions(+), 88 deletions(-)
next reply other threads:[~2019-05-09 7:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 7:16 Christoph Hellwig [this message]
2019-05-09 16:25 ` 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=20190509071634.GA604@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
all inboxes | Powered by JetHome®