From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: aneesh.kumar@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-6.3-5 tag
Date: Sun, 16 Apr 2023 19:52:23 +1000 [thread overview]
Message-ID: <87r0ski27c.fsf@mpe.ellerman.id.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull another powerpc fix for 6.3:
The following change since commit eca9f6e6f83b6725b84e1c76fdde19b003cff0eb:
powerpc/pseries/vas: Ignore VAS update for DLPAR if copy/paste is not enabled (2023-03-29 23:01:35 +1100)
is available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-6.3-5
for you to fetch up to b277fc793daf258877b4c0744b52f69d6e6ba22e:
powerpc/papr_scm: Update the NUMA distance table for the target node (2023-04-04 22:08:35 +1000)
- ------------------------------------------------------------------
powerpc fixes for 6.3 #5
- A fix for NUMA distance handling in the pseries SCM (pmem) driver.
Thanks to: Aneesh Kumar K.V
- ------------------------------------------------------------------
Aneesh Kumar K.V (1):
powerpc/papr_scm: Update the NUMA distance table for the target node
arch/powerpc/mm/numa.c | 1 +
arch/powerpc/platforms/pseries/papr_scm.c | 7 +++++++
2 files changed, 8 insertions(+)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmQ7xSEACgkQUevqPMjh
pYB+dRAAq1ochTHshZ1uYXI2WdPMV5L+RYWp+2VNEufRBFmguOnfYTrICWvhCD03
6EzrU9foN8wsmZXlFCnGUiFRHlymUDbh6e9AeOwYhlD7UhfMN8KcABjtUVQuGjen
DF63mu6vtOn0/oE8J/dMdJ+ZMqsfb2kGzQKFgAwiqqi3izwVVpInLuNyZ8CgDKss
Zpeg92NNidaODhUhsRJMPI7easWUzZWY3cXmOd8hWHirCKCPRrP5B12p39B1EQ7W
S8iUsidQIkfAr2Ti9+4JThqnr99EuRZigqm+FbmFqD4L21FsJlIk7qtAPHjKJ7E3
+K5vjYc9dWQra04i+IRt42Yn4lc37kn50OKAbsjxlE7WkNqvZO1PPNnMpbtfhbOU
k+qDEJr6WrmV1c/y6BQ2iMvYcstVisG7eDBo2c4iesFI0QVJZ8/vTJiN7GiLZYQV
wC0C7WIw8MXcwjtuID4uofdoIfMRnHlL/j9j49pRW3DeaIxyXZ8H90bqUXIiLqN4
lntl8mt2Xgl3vwUbtbahh/qGYwpBBNg0pxuCiisuGL8y++MA/xaXyfUbrvNrGPh2
HWvAPBdf7aYtqFnTdtfLXrefTFnqmuKA4qmW8tqM2zRwy/LFQl8nMVJwz3AMD/FV
SP/Rwj5YdlKOJKYAcms45+fn3akFy01ga2pC3SqzW1Am8772LpY=
=Q8fq
-----END PGP SIGNATURE-----
next reply other threads:[~2023-04-16 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 9:52 Michael Ellerman [this message]
2023-04-16 17:43 ` [GIT PULL] Please pull powerpc/linux.git powerpc-6.3-5 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=87r0ski27c.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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