From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: robh@kernel.org, gbatra@linux.vnet.ibm.com,
rdunlap@infradead.org, linux-kernel@vger.kernel.org,
nathan@kernel.org, jgg@nvidia.com, linuxppc-dev@lists.ozlabs.org,
hbathini@linux.ibm.com
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-6.4-2 tag
Date: Sun, 21 May 2023 11:59:02 +1000 [thread overview]
Message-ID: <87lehizbq1.fsf@mail.lhotse> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull powerpc fixes for 6.4:
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-6.4-2
for you to fetch changes up to 1f7aacc5eb9ed2cc17be7a90da5cd559effb9d59:
powerpc/iommu: Incorrect DDW Table is referenced for SR-IOV device (2023-05-17 00:54:55 +1000)
- ------------------------------------------------------------------
powerpc fixes for 6.4 #2
- Fix broken soft dirty tracking when using the Radix MMU (>= P9).
- Fix ISA mapping when "ranges" property is not present, for PASemi Nemo boards.
- Fix a possible WARN_ON_ONCE hitting in BPF extable handling.
- Fix incorrect DMA address handling when using 2MB TCEs.
- Fix a bug in IOMMU table handling for SR-IOV devices.
- Fix the recent rework of IOMMU handling which left arch code calling clean
up routines that are handled by the IOMMU core.
- A few assorted build fixes.
Thanks to: Christian Zigotzky, Dan Horák, Gaurav Batra, Hari Bathini, Jason
Gunthorpe, Nathan Chancellor, Naveen N. Rao, Nicholas Piggin, Pali Rohár, Randy
Dunlap, Rob Herring.
- ------------------------------------------------------------------
Gaurav Batra (2):
powerpc/iommu: DMA address offset is incorrectly calculated with 2MB TCEs
powerpc/iommu: Incorrect DDW Table is referenced for SR-IOV device
Hari Bathini (1):
powerpc/bpf: populate extable entries only during the last pass
Jason Gunthorpe (1):
powerpc/iommu: Remove iommu_del_device()
Michael Ellerman (2):
powerpc/64s/radix: Fix soft dirty tracking
powerpc/crypto: Fix aes-gcm-p10 build when VSX=n
Nathan Chancellor (1):
powerpc/boot: Disable power10 features after BOOTAFLAGS assignment
Randy Dunlap (1):
powerpc/fsl_uli1575: fix kconfig warnings and build errors
Rob Herring (1):
powerpc/isa-bridge: Fix ISA mapping when "ranges" is not present
arch/powerpc/boot/Makefile | 6 ++--
arch/powerpc/crypto/Kconfig | 2 +-
arch/powerpc/include/asm/iommu.h | 5 ---
arch/powerpc/kernel/dma-iommu.c | 4 ++-
arch/powerpc/kernel/iommu.c | 28 ++++-----------
arch/powerpc/kernel/isa-bridge.c | 5 +--
arch/powerpc/mm/book3s64/radix_pgtable.c | 4 +--
arch/powerpc/net/bpf_jit_comp.c | 2 ++
arch/powerpc/platforms/Kconfig | 1 +
arch/powerpc/platforms/powernv/pci.c | 25 -------------
arch/powerpc/platforms/pseries/iommu.c | 38 +++++---------------
11 files changed, 32 insertions(+), 88 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmRpeqIACgkQUevqPMjh
pYA2fQ/7BZucOtUs36IjCBHUMd+l5De01lPzoErQ6m3r3uwpEgymXw531NlTv+Sq
eGfwUDTuYts4pXW5ELAeVHsW7115lou2775Th2kbjcnGR2PtMFeDfnAgXb5mTFSI
L7FkUm2Z/V5tEGO9QNVIcwmrx8uK743Jou+HWAkMGqoopnomPjLspirZGAtOLSVk
pmyzWIRyfeaSm5elAx37vFzgQ+uJtJ9rhf8YaLzgjOX309jFoOhqd1O9tNC8rfFH
59gxeSW2gzdnKO/GzU3x5fDLCxqPCrRG8KnM8RDTjFIvRQRZrF/fAN3tYhYew+IT
omFteOW89tZS2JJbmZyTQPLIh2Nkvi0iEItwC7i1rz1nVmTTy3vPD3bC3xfoNH+2
aepvt4KuLmcJ62M3MZNwMfPcdfCwqCg7G1+ORUVdnElYO9r8weOBNkHIYqIFVuQX
LRMu2kUmMVYaqm4YBRrMKCvZX1zNNJvPFRlQI8WjPG6oOTLQILee5MUmdeCIEa9K
piMkA+YoDfaJ2l9FCA48MJiueSRgkDAW/RsI/ozu6BE1Ba2ndy0JL/4qMpInsh3T
3/fwnynLX3A28wFCJFNOykjvGb6X90gRzQ48Vga9U0yGNhPA+f4Xk9b1JslWb8l3
nn78rof3w2wkYDOUSnlDtSFzS7O2WYfRh5c5UdZxfpo4OV6RbAE=
=nuS4
-----END PGP SIGNATURE-----
next reply other threads:[~2023-05-21 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 1:59 Michael Ellerman [this message]
2023-05-21 18:58 ` [GIT PULL] Please pull powerpc/linux.git powerpc-6.4-2 tag 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=87lehizbq1.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=gbatra@linux.vnet.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nathan@kernel.org \
--cc=rdunlap@infradead.org \
--cc=robh@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