From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: nathanl@linux.ibm.com, puranjay@kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
samuel.holland@sifive.com
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-6.10-2 tag
Date: Sun, 02 Jun 2024 09:57:33 +1000 [thread overview]
Message-ID: <87jzj82p3m.fsf@mail.lhotse> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull powerpc fixes for 6.10:
The following changes since commit 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0:
Linux 6.10-rc1 (2024-05-26 15:20:12 -0700)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-6.10-2
for you to fetch changes up to be2fc65d66e0406cc9d39d40becaecdf4ee765f3:
powerpc: Limit ARCH_HAS_KERNEL_FPU_SUPPORT to PPC64 (2024-05-30 22:57:27 +1000)
- ------------------------------------------------------------------
powerpc fixes for 6.10 #2
- Enforce full ordering for ATOMIC operations with BPF_FETCH.
- Fix uaccess build errors seen with GCC 13/14.
- Fix build errors on ppc32 due to ARCH_HAS_KERNEL_FPU_SUPPORT.
- Drop error message from lparcfg guest name lookup.
Thanks to: Christophe Leroy, Guenter Roeck, Nathan Lynch, Naveen N Rao, Puranjay
Mohan, Samuel Holland.
- ------------------------------------------------------------------
Michael Ellerman (2):
powerpc/uaccess: Fix build errors seen with GCC 13/14
powerpc/uaccess: Use YZ asm constraint for ld
Nathan Lynch (1):
powerpc/pseries/lparcfg: drop error message from guest name lookup
Puranjay Mohan (1):
powerpc/bpf: enforce full ordering for ATOMIC operations with BPF_FETCH
Samuel Holland (1):
powerpc: Limit ARCH_HAS_KERNEL_FPU_SUPPORT to PPC64
arch/powerpc/Kconfig | 2 +-
arch/powerpc/include/asm/uaccess.h | 27 ++++++++++++++++++++
arch/powerpc/net/bpf_jit_comp32.c | 12 +++++++++
arch/powerpc/net/bpf_jit_comp64.c | 12 +++++++++
arch/powerpc/platforms/pseries/lparcfg.c | 4 +--
5 files changed, 54 insertions(+), 3 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmZbtSIACgkQUevqPMjh
pYALTQ//YkCAb17EW6iQfmcuaq7Amhz5QUDUU3TFhfcmmuDd3Fw3bh9sppF+so0S
UsZpBRgY9C6xFkOqpyrqj9KOSXNsWE5m46Hp0Cl7BlkdeM2c68T77BxN5pEcnI4i
so64UHaLDI0miirQE25ihA4BdmtzAfw6PL6vubcBoLrlSWktXDQXBZb0EkOeYNiR
QI+4EnwfkUiw+55eXEHoWIwWuyW7oMd2px8wXEnb9daOxu7NqDhKINVYN8g0If8u
m90egWk56gq1A/ei43zeqPQAKi8hvQe93+tkmCI7NkJCx+YrYmUStqIC/4/iZlJd
XMaUre8mckU6eWRfUL5G28BDETtNm3t2TlflJ+GK1XvLd0LOj2SEk0f5i2bXA6ey
o1ISDVE3dRbS3CzfiZw8S7QvJiCeqBU1d3gMjNge+c1iSG0rgd20tMA17+SEKaHn
W2tSZev6P9vbpF+9R0kxvyCRQ3EmPeOReSk0XIXU+X0V2NFIEIzQJMS/2NL2Mro8
O5tj3elpRbqSa/rEUUQymUpQ3qEkTfoFrIAiCkFvu+OcAtq26OL18olxWo0RF9Fg
8ElHjsGLMDNPyTrBIIIegcgsX+/fvGbwg5NpQlXOD564Y0cMfYi8kYwgU6Z9ism1
YfKFgvrj1akmTMrZobqZ1N0tCjXZVbRP+ykyT6uUtG7ut4v4d8U=
=+3xo
-----END PGP SIGNATURE-----
next reply other threads:[~2024-06-01 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 23:57 Michael Ellerman [this message]
2024-06-02 0:44 ` [GIT PULL] Please pull powerpc/linux.git powerpc-6.10-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=87jzj82p3m.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nathanl@linux.ibm.com \
--cc=puranjay@kernel.org \
--cc=samuel.holland@sifive.com \
--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).