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.11
Date: Fri, 31 May 2024 14:31:52 +0200	[thread overview]
Message-ID: <ZlnDOBd2X3T4fiev@infradead.org> (raw)

The following changes since commit c760b3725e52403dc1b28644fb09c47a83cacea6:

  Merge tag 'mm-nonmm-stable-2024-05-22-17-30' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm (2024-05-22 18:59:29 -0700)

are available in the Git repository at:

  git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-6.10-2024-05-31

for you to fetch changes up to 82d71b53d7e732ede6028591342bdc80fabfa29f:

  Documentation/core-api: correct reference to SWIOTLB_DYNAMIC (2024-05-27 16:52:09 +0200)

----------------------------------------------------------------
dma-mapping fixes for Linux 6.10

 - dma-mapping benchmark error handling fixes (Fedor Pchelkin)
 - correct a config symbol reference in the DMA API documentation
   (Lukas Bulwahn)

----------------------------------------------------------------
Fedor Pchelkin (4):
      dma-mapping: benchmark: fix up kthread-related error handling
      dma-mapping: benchmark: avoid needless copy_to_user if benchmark fails
      dma-mapping: benchmark: fix node id validation
      dma-mapping: benchmark: handle NUMA_NO_NODE correctly

Lukas Bulwahn (1):
      Documentation/core-api: correct reference to SWIOTLB_DYNAMIC

 Documentation/core-api/swiotlb.rst |  2 +-
 kernel/dma/map_benchmark.c         | 25 ++++++++++++++++---------
 2 files changed, 17 insertions(+), 10 deletions(-)

             reply	other threads:[~2024-05-31 12:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31 12:31 Christoph Hellwig [this message]
2024-05-31 19:20 ` [GIT PULL] dma-mapping fixes for Linux 6.11 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=ZlnDOBd2X3T4fiev@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