linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] dma-mapping fixes for Linux 5.15
Date: Wed, 20 Oct 2021 19:14:51 +0200	[thread overview]
Message-ID: <YXBOiy+yS4pwwHeQ@infradead.org> (raw)

The following changes since commit 59583f747664046aaae5588d56d5954fab66cce8:

  sparc32: page align size in arch_dma_alloc (2021-09-14 14:35:17 +0200)

are available in the Git repository at:

  git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.15-2

for you to fetch changes up to c2bbf9d1e9ac7d4fdd503b190bc1ba8a6302bc49:

  dma-debug: teach add_dma_entry() about DMA_ATTR_SKIP_CPU_SYNC (2021-10-18 12:46:45 +0200)

----------------------------------------------------------------
dma-mapping fixes for Linux 5.15

 - fix more dma-debug fallout (Gerald Schaefer, Hamza Mahfooz)
 - fix a kerneldoc warning (Logan Gunthorpe)

----------------------------------------------------------------
Gerald Schaefer (1):
      dma-debug: fix sg checks in debug_dma_map_sg()

Hamza Mahfooz (1):
      dma-debug: teach add_dma_entry() about DMA_ATTR_SKIP_CPU_SYNC

Logan Gunthorpe (1):
      dma-mapping: fix the kerneldoc for dma_map_sgtable()

 kernel/dma/debug.c   | 36 ++++++++++++++++++++----------------
 kernel/dma/debug.h   | 24 ++++++++++++++++--------
 kernel/dma/mapping.c | 24 ++++++++++++------------
 3 files changed, 48 insertions(+), 36 deletions(-)

             reply	other threads:[~2021-10-20 17:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 17:14 Christoph Hellwig [this message]
2021-10-20 20:45 ` [GIT PULL] dma-mapping fixes for Linux 5.15 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2021-09-17 11:22 Christoph Hellwig
2021-09-17 16:19 ` Linus Torvalds
2021-09-17 16:29 ` 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=YXBOiy+yS4pwwHeQ@infradead.org \
    --to=hch@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --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;
as well as URLs for NNTP newsgroup(s).