public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 fixes for Linux 6.6
Date: Sat, 9 Sep 2023 05:46:57 -0300	[thread overview]
Message-ID: <ZPwxAWSXvmJNgj0X@infradead.org> (raw)

The following changes since commit d069ed288ac74c24e2b1c294aa9445c80ed6c518:

  swiotlb: optimize get_max_slots() (2023-08-08 10:29:21 -0700)

are available in the Git repository at:

  git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-6.6-2023-09-09

for you to fetch changes up to f875db4f20f4ec2e4fa3b3be0e5081976e0b5dad:

  Revert "dma-contiguous: check for memory region overlap" (2023-09-08 05:58:32 -0300)

----------------------------------------------------------------
dma-mapping fixes for Linux 6.6

 - move a dma-debug call that prints a message out from a lock that's
   causing problems with the lock order in serial drivers (Sergey Senozhatsky)
 - fix the CONFIG_DMA_NUMA_CMA Kconfig entry to have the right dependency
   on not default to y (Christoph Hellwig)
 - move an ifdef a bit to remove a __maybe_unused that seems to trip up
   some sensitivities (Christoph Hellwig)
 - revert a bogus check in the CMA allocator (Zhenhua Huang)

----------------------------------------------------------------
Christoph Hellwig (2):
      dma-contiguous: fix the Kconfig entry for CONFIG_DMA_NUMA_CMA
      dma-pool: remove a __maybe_unused label in atomic_pool_expand

Sergey Senozhatsky (1):
      dma-debug: don't call __dma_entry_alloc_check_leak() under free_entries_lock

Zhenhua Huang (1):
      Revert "dma-contiguous: check for memory region overlap"

 kernel/dma/Kconfig      |  2 +-
 kernel/dma/contiguous.c |  5 -----
 kernel/dma/debug.c      | 20 +++++++++++++++-----
 kernel/dma/pool.c       |  4 ++--
 4 files changed, 18 insertions(+), 13 deletions(-)

             reply	other threads:[~2023-09-09  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09  8:46 Christoph Hellwig [this message]
2023-09-09 18:53 ` [GIT PULL] dma-mapping fixes for Linux 6.6 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2023-09-30 17:23 Christoph Hellwig
2023-09-30 18:12 ` 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=ZPwxAWSXvmJNgj0X@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