The Linux Kernel Mailing List
 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.2
Date: Tue, 13 Dec 2022 17:42:35 +0100	[thread overview]
Message-ID: <Y5ire5HIAi/kc3cg@infradead.org> (raw)

The following changes since commit 30a0b95b1335e12efef89dd78518ed3e4a71a763:

  Linux 6.1-rc3 (2022-10-30 15:19:28 -0700)

are available in the Git repository at:

  git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-6.2-2022-12-13

for you to fetch changes up to ffcb754584603adf7039d7972564fbf6febdc542:

  dma-mapping: reject __GFP_COMP in dma_alloc_attrs (2022-11-21 09:37:20 +0100)

----------------------------------------------------------------
dma-mapping updates for Linux 2.6

 - reduce the swiotlb buffer size on allocation failure
   (Alexey Kardashevskiy)
 - clean up passing of bogus GFP flags to the dma-coherent allocator
   (Christoph Hellwig)

----------------------------------------------------------------
Alexey Kardashevskiy (1):
      swiotlb: reduce the swiotlb buffer size on allocation failure

Christoph Hellwig (7):
      media: videobuf-dma-contig: use dma_mmap_coherent
      RDMA/hfi1: don't pass bogus GFP_ flags to dma_alloc_coherent
      RDMA/qib: don't pass bogus GFP_ flags to dma_alloc_coherent
      cnic: don't pass bogus GFP_ flags to dma_alloc_coherent
      s390/ism: don't pass bogus GFP_ flags to dma_alloc_coherent
      ALSA: memalloc: don't pass bogus GFP_ flags to dma_alloc_*
      dma-mapping: reject __GFP_COMP in dma_alloc_attrs

 arch/arm/mm/dma-mapping.c                     | 17 --------
 drivers/infiniband/hw/hfi1/init.c             | 21 ++-------
 drivers/infiniband/hw/qib/qib_iba6120.c       |  2 +-
 drivers/infiniband/hw/qib/qib_init.c          | 21 ++-------
 drivers/iommu/dma-iommu.c                     |  3 --
 drivers/media/v4l2-core/videobuf-dma-contig.c | 22 ++++------
 drivers/net/ethernet/broadcom/cnic.c          |  6 +--
 drivers/s390/net/ism_drv.c                    |  3 +-
 kernel/dma/mapping.c                          |  8 ++++
 kernel/dma/swiotlb.c                          | 63 +++++++++++++++++----------
 sound/core/memalloc.c                         |  5 +--
 11 files changed, 69 insertions(+), 102 deletions(-)

             reply	other threads:[~2022-12-13 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 16:42 Christoph Hellwig [this message]
2022-12-13 18:13 ` [GIT PULL] dma-mapping updates for Linux 6.2 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=Y5ire5HIAi/kc3cg@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