From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
srikar@linux.vnet.ibm.com
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-5.14-4 tag
Date: Sun, 01 Aug 2021 23:16:16 +1000 [thread overview]
Message-ID: <87y29lz4nz.fsf@mpe.ellerman.id.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull some more powerpc fixes for 5.14:
The following changes since commit d9c57d3ed52a92536f5fa59dc5ccdd58b4875076:
KVM: PPC: Book3S HV Nested: Sanitise H_ENTER_NESTED TM state (2021-07-23 16:19:38 +1000)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-5.14-4
for you to fetch changes up to a88603f4b92ecef9e2359e40bcb99ad399d85dd7:
powerpc/vdso: Don't use r30 to avoid breaking Go lang (2021-07-29 23:13:12 +1000)
- ------------------------------------------------------------------
powerpc fixes for 5.14 #4
- Don't use r30 in VDSO code, to avoid breaking existing Go lang programs.
- Change an export symbol to allow non-GPL modules to use spinlocks again.
Thanks to: Paul Menzel, Srikar Dronamraju.
- ------------------------------------------------------------------
Michael Ellerman (2):
Merge branch 'fixes' into next
powerpc/vdso: Don't use r30 to avoid breaking Go lang
Srikar Dronamraju (1):
powerpc/pseries: Fix regression while building external modules
arch/powerpc/kernel/vdso64/Makefile | 7 +++++++
arch/powerpc/platforms/pseries/setup.c | 2 +-
2 files changed, 8 insertions(+), 1 deletion(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmEGnawACgkQUevqPMjh
pYApeg/9E8l0SD4+NzC0ZwZxQ7sAxufs2X9uugWeTxjEMF3BvhnzAcfF3qPewP0+
Huy7UwhHYKMBGT9jpqqQuLMfxasbihizesdP89BAVIhzyL6odg6/fo+KaBVVADYr
F+jHugUXoimS47IntMyQa2HANpCLjl66ZIYWgqytuLgx8jnvIzCGbLmrTN/F4FTS
7mkNO7+wOmwEi4y3p1cCVnkBd7qkQnjkRgpwS/FQLbtE6G3qkcNhNK1v5AAuSblJ
eLJ0Lp/+z1OYKA/BSmyM5Aj7kytn9f5UjA2jBtS9O0sfcd19g5LTdKXxPftaAgO3
eNr947NTztadHQLkLdeeVCDyqrUnAZFZ7f4kn16JIc27ObCWFhFC/OQR+Ba9KGbN
0hgwVREZ+aqdquYPbqZTj4VWLeEQflgk9zfp9sZquZvOHoknBsvUmzvL24LLE8hw
ETYEoQwdtBZfCNCbEofCIu3BZXtvt99FUsJo65sUKGty7Vb2iuo3jq85jsgwrh21
8OhhQ1njfbw+InMYJO1LgFVAXE9f5FDLaV1oMJkkO6vhDZ73Lsac7AG5MP7TrB+z
dbT0BTfB6nevXzf+JX1OxHZtCXVriXuFWrzZpQVX65zkzbO4N6Q3+Wk28PmMU67P
oiDsdZWjBxk9rA4xXNGof6AIKr3SDt3/u2kMa/iR5r/mq1itZRk=
=dB85
-----END PGP SIGNATURE-----
next reply other threads:[~2021-08-01 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 13:16 Michael Ellerman [this message]
2021-08-01 19:28 ` [GIT PULL] Please pull powerpc/linux.git powerpc-5.14-4 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=87y29lz4nz.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=srikar@linux.vnet.ibm.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