From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: [GIT PULL] dma-mapping updates for Linux 6.13
Date: Tue, 19 Nov 2024 18:06:25 +0100 [thread overview]
Message-ID: <ZzzFkZHDxrgq2B9i@infradead.org> (raw)
The following changes since commit e42b1a9a2557aa94fee47f078633677198386a52:
Merge tag 'spi-fix-v6.12-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi (2024-10-28 11:16:33 -1000)
are available in the Git repository at:
git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-6.13-2024-11-19
for you to fetch changes up to 22293c33738c14bb84b9d3e771bc37150e7cf8e7:
dma-mapping: save base/size instead of pointer to shared DMA pool (2024-11-14 10:45:09 +0100)
----------------------------------------------------------------
dma-mapping updates for Linux 6.13
- improve the DMA API tracing code (Sean Anderson)
- misc cleanups (Christoph Hellwig, Sui Jingfeng)
- fix pointer abuse when finding the shared DMA pool (Geert Uytterhoeven)
- fix a deadlock in dma-debug (Levi Yun)
----------------------------------------------------------------
Christoph Hellwig (3):
dma-debug: store a phys_addr_t in struct dma_debug_entry
dma-debug: remove DMA_API_DEBUG_SG
dma-mapping: drop unneeded includes from dma-mapping.h
Geert Uytterhoeven (1):
dma-mapping: save base/size instead of pointer to shared DMA pool
Levi Yun (1):
dma-debug: fix a possible deadlock on radix_lock
Sean Anderson (5):
dma-mapping: use macros to define events in a class
dma-mapping: trace dma_alloc/free direction
dma-mapping: use trace_dma_alloc for dma_alloc* instead of using trace_dma_map
dma-mapping: trace more error paths
dma-mapping: fix swapped dir/flags arguments to trace_dma_alloc_sgt_err
Sui Jingfeng (1):
dma-mapping: remove an outdated comment from dma-map-ops.h
arch/powerpc/platforms/pseries/svm.c | 1 +
include/linux/dma-map-ops.h | 2 +-
include/linux/dma-mapping.h | 4 -
include/trace/events/dma.h | 213 ++++++++++++++++++++++++++++-------
kernel/dma/Kconfig | 17 ---
kernel/dma/coherent.c | 14 ++-
kernel/dma/debug.c | 89 ++++++---------
kernel/dma/mapping.c | 37 ++++--
8 files changed, 242 insertions(+), 135 deletions(-)
next reply other threads:[~2024-11-19 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 17:06 Christoph Hellwig [this message]
2024-11-21 21:20 ` pr-tracker-bot
2024-11-21 21:20 ` 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=ZzzFkZHDxrgq2B9i@infradead.org \
--to=hch@infradead.org \
--cc=iommu@lists.linux.dev \
--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®