From: Joerg Roedel <joro@8bytes.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: [git pull] IOMMU Fixes for Linux v6.5-rc1
Date: Sat, 15 Jul 2023 09:15:51 +0200 [thread overview]
Message-ID: <ZLJHpx42Da4LA_ng@8bytes.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
Hi Linus,
The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:
Linux 6.5-rc1 (2023-07-09 13:53:13 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v6.5-rc1
for you to fetch changes up to c20ecf7bb6153149b81a9277eda23398957656f2:
iommu/sva: Fix signedness bug in iommu_sva_alloc_pasid() (2023-07-14 14:53:19 +0200)
----------------------------------------------------------------
IOMMU Fixes for Linux v6.5-rc1
Including:
- Fix a regression causing a crash on sysfs access of iommu-group
specific files
- Fix signedness bug in SVA code
----------------------------------------------------------------
Dan Carpenter (1):
iommu/sva: Fix signedness bug in iommu_sva_alloc_pasid()
Jason Gunthorpe (1):
iommu: Fix crash during syfs iommu_groups/N/type
drivers/iommu/iommu-sva.c | 3 ++-
drivers/iommu/iommu.c | 27 ++++++++++++++-------------
2 files changed, 16 insertions(+), 14 deletions(-)
Please pull.
Thanks,
Joerg
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-07-15 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 7:15 Joerg Roedel [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 20:31 [git pull] IOMMU Fixes for Linux v6.5-rc1 Joerg Roedel
2023-07-15 3:19 ` Linus Torvalds
2023-07-15 7:12 ` Joerg Roedel
2023-07-15 15:57 ` 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=ZLJHpx42Da4LA_ng@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.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