All of lore.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 updates for Linux 6.7
Date: Mon, 30 Oct 2023 15:08:41 +0100	[thread overview]
Message-ID: <ZT-46QZiN8b37Swy@infradead.org> (raw)

Hi Linus,

the Kconfig dependencies added in this branch caught configuration issues
in a riscv platform.  The fixes for that went into th soc tree, so it
if you want to avoid them it might make sense to pull this branch after
the soc tree.

The following changes since commit ce55c22ec8b223a90ff3e084d842f73cfba35588:

  Merge tag 'net-6.6-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2023-10-19 12:08:18 -0700)

are available in the Git repository at:

  git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-6.7-2023-10-30

for you to fetch changes up to 36d91e851598a9ea523ad4681dd11fa661d59695:

  dma-debug: Fix a typo in a debugging eye-catcher (2023-10-23 07:52:54 +0200)

----------------------------------------------------------------
dma-mapping updates for Linux 6.7

 - get rid of the fake support for coherent DMA allocation on coldfire with
   caches (Christoph Hellwig)
 - add a few Kconfig dependencies so that Kconfig catches the use of
   invalid configurations (Christoph Hellwig)
 - fix a type in dma-debug output (Chuck Lever)
 - rewrite a comment in swiotlb (Sean Christopherson)

----------------------------------------------------------------
Christoph Hellwig (8):
      dma-direct: add dependencies to CONFIG_DMA_GLOBAL_POOL
      dma-direct: add a CONFIG_ARCH_HAS_DMA_ALLOC symbol
      dma-direct: simplify the use atomic pool logic in dma_direct_alloc
      dma-direct: warn when coherent allocations aren't supported
      m68k: use the coherent DMA code for coldfire without data cache
      net: fec: use dma_alloc_noncoherent for data cache enabled coldfire
      m68k: don't provide arch_dma_alloc for nommu/coldfire
      m68k: remove unused includes from dma.c

Chuck Lever (1):
      dma-debug: Fix a typo in a debugging eye-catcher

Sean Christopherson (1):
      swiotlb: rewrite comment explaining why the source is preserved on DMA_FROM_DEVICE

 arch/arm/Kconfig                          |  1 +
 arch/m68k/Kconfig                         |  6 +--
 arch/m68k/Kconfig.cpu                     | 12 +++++
 arch/m68k/kernel/Makefile                 |  2 +-
 arch/m68k/kernel/dma.c                    | 34 +-----------
 arch/parisc/Kconfig                       |  1 +
 drivers/net/ethernet/freescale/fec_main.c | 86 +++++++++++++++++++++++++++----
 kernel/dma/Kconfig                        | 11 ++++
 kernel/dma/debug.c                        |  2 +-
 kernel/dma/direct.c                       | 37 +++++--------
 kernel/dma/swiotlb.c                      | 12 +++--
 11 files changed, 127 insertions(+), 77 deletions(-)

             reply	other threads:[~2023-10-30 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 14:08 Christoph Hellwig [this message]
2023-10-31  8:07 ` [GIT PULL] dma-mapping updates for Linux 6.7 Geert Uytterhoeven
2023-11-02  0:01 ` 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=ZT-46QZiN8b37Swy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.