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 Linux 5.16
Date: Tue, 9 Nov 2021 14:53:16 +0100 [thread overview]
Message-ID: <YYp9TAVLFsxqfVx7@infradead.org> (raw)
Just a small set of changes this time. The request dma_direct_alloc
cleanups are still under review and haven't made the cut.
The following changes since commit 519d81956ee277b4419c723adfb154603c2565ba:
Linux 5.15-rc6 (2021-10-17 20:00:13 -1000)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.16
for you to fetch changes up to 9fbd8dc19aa57ec8fe92606043199919527cd9be:
dma-mapping: use 'bitmap_zalloc()' when applicable (2021-10-27 08:20:09 +0200)
----------------------------------------------------------------
dma-mapping updates for Linux 5.16
- convert sparc32 to the generic dma-direct code
- use bitmap_zalloc (Christophe JAILLET)
----------------------------------------------------------------
Christoph Hellwig (3):
sparc32: remove the call to dma_make_coherent in arch_dma_free
sparc32: remove dma_make_coherent
sparc32: use DMA_DIRECT_REMAP
Christophe JAILLET (1):
dma-mapping: use 'bitmap_zalloc()' when applicable
arch/sparc/Kconfig | 3 +-
arch/sparc/kernel/ioport.c | 76 +++++-----------------------------------------
kernel/dma/coherent.c | 5 ++-
3 files changed, 12 insertions(+), 72 deletions(-)
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2021-11-09 13:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 13:53 Christoph Hellwig [this message]
2021-11-09 19:31 ` [GIT PULL] dma-mapping updates for Linux 5.16 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=YYp9TAVLFsxqfVx7@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