From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: [GIT PULL] dma-mapping fix for Linux 6.14
Date: Fri, 21 Mar 2025 00:21:15 +0100 [thread overview]
Message-ID: <20250320232115.3940-1-m.szyprowski@samsung.com> (raw)
In-Reply-To: <CGME20250320232137eucas1p2f877454de65336d638b200d920ccf2f3@eucas1p2.samsung.com>
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/mszyprowski/linux.git tags/dma-mapping-6.14-2025-03-21
for you to fetch changes up to 8324993f60305e50f27b98358b01b9837e10d159:
dma-mapping: fix missing clear bdr in check_ram_in_range_map() (2025-03-12 13:41:44 +0100)
----------------------------------------------------------------
dma-mapping fix for Linux 6.14
- fix missing clear bdr in check_ram_in_range_map()
(Baochen Qiang)
----------------------------------------------------------------
Baochen Qiang (1):
dma-mapping: fix missing clear bdr in check_ram_in_range_map()
kernel/dma/direct.c | 28 ++++++++++++++++++----------
1 file changed, 18 insertions(+), 10 deletions(-)
----------------------------------------------------------------
Thanks!
Best regards
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next parent reply other threads:[~2025-03-20 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250320232137eucas1p2f877454de65336d638b200d920ccf2f3@eucas1p2.samsung.com>
2025-03-20 23:21 ` Marek Szyprowski [this message]
2025-03-20 23:59 ` 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=20250320232115.3940-1-m.szyprowski@samsung.com \
--to=m.szyprowski@samsung.com \
--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
all inboxes | Powered by JetHome®