From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [GIT PULL] second round of dma-mapping updates for Linux 5.18
Date: Sun, 3 Apr 2022 14:22:47 +0200 [thread overview]
Message-ID: <YkmRl8McdwST4cII@infradead.org> (raw)
The following changes since commit 5efabdadcf4a5b9a37847ecc85ba71cf2eff0fcf:
Merge tag 'devicetree-fixes-for-5.18-1' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux (2022-03-29 08:55:16 -0700)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.18-1
for you to fetch changes up to 4fe87e818ea492ade079cc01a31d088e445f8539:
dma-mapping: move pgprot_decrypted out of dma_pgprot (2022-04-01 06:46:51 +0200)
----------------------------------------------------------------
second round of dma-mapping updates for 5.18
- fix a regression in dma remap handling vs AMD memory encryption (me)
- finally kill off the legacy PCI DMA API (Christophe JAILLET)
----------------------------------------------------------------
Christoph Hellwig (2):
PCI/doc: cleanup references to the legacy PCI DMA API
dma-mapping: move pgprot_decrypted out of dma_pgprot
Christophe JAILLET (1):
PCI: Remove the deprecated "pci-dma-compat.h" API
Documentation/PCI/pci.rst | 14 ++---
include/linux/pci-dma-compat.h | 129 -----------------------------------------
include/linux/pci.h | 3 +-
kernel/dma/direct.c | 10 +++-
kernel/dma/mapping.c | 2 -
5 files changed, 16 insertions(+), 142 deletions(-)
delete mode 100644 include/linux/pci-dma-compat.h
next reply other threads:[~2022-04-03 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 12:22 Christoph Hellwig [this message]
2022-04-03 20:29 ` [GIT PULL] second round of dma-mapping updates for Linux 5.18 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=YkmRl8McdwST4cII@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