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.19
Date: Mon, 6 Jun 2022 08:38:45 +0200 [thread overview]
Message-ID: <Yp2g9SGrXn0eSvnA@infradead.org> (raw)
[I really wanted to send these before -rc1, but the fact that today is
a public holiday here really confused me and messed up my schedule]
The following changes since commit 4a37f3dd9a83186cb88d44808ab35b78375082c9:
dma-direct: don't over-decrypt memory (2022-05-23 15:25:40 +0200)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.19-2022-06-06
for you to fetch changes up to e15db62bc5648ab459a570862f654e787c498faf:
swiotlb: fix setting ->force_bounce (2022-06-02 07:17:59 +0200)
----------------------------------------------------------------
dma-mapping fixes for Linux 5.19
- fix a regressin in setting swiotlb ->force_bounce (me)
- make dma-debug less chatty (Rob Clark)
----------------------------------------------------------------
Christoph Hellwig (1):
swiotlb: fix setting ->force_bounce
Rob Clark (1):
dma-debug: make things less spammy under memory pressure
kernel/dma/debug.c | 2 +-
kernel/dma/swiotlb.c | 14 ++++++--------
2 files changed, 7 insertions(+), 9 deletions(-)
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2022-06-06 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 6:38 Christoph Hellwig [this message]
2022-06-07 0:59 ` [GIT PULL] dma-mapping fixes for 5.19 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=Yp2g9SGrXn0eSvnA@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