From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linuxppc-dev@lists.ozlabs.org, anders.roxell@linaro.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-5.17-4 tag
Date: Fri, 18 Feb 2022 13:54:05 +1100 [thread overview]
Message-ID: <87pmnknauq.fsf@mpe.ellerman.id.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull some more powerpc fixes for 5.17:
The following changes since commit 26291c54e111ff6ba87a164d85d4a4e134b7315c:
Linux 5.17-rc2 (2022-01-30 15:37:07 +0200)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-5.17-4
for you to fetch changes up to fe663df7825811358531dc2e8a52d9eaa5e3515e:
powerpc/lib/sstep: fix 'ptesync' build error (2022-02-15 22:31:35 +1100)
- ------------------------------------------------------------------
powerpc fixes for 5.17 #4
- Fix boot failure on 603 with DEBUG_PAGEALLOC and KFENCE.
- Fix 32-build with newer binutils that rejects 'ptesync' etc.
Thanks to: Anders Roxell, Christophe Leroy, Maxime Bizon.
- ------------------------------------------------------------------
Anders Roxell (1):
powerpc/lib/sstep: fix 'ptesync' build error
Christophe Leroy (1):
powerpc/603: Fix boot failure with DEBUG_PAGEALLOC and KFENCE
arch/powerpc/kernel/head_book3s_32.S | 4 ++--
arch/powerpc/lib/sstep.c | 2 ++
2 files changed, 4 insertions(+), 2 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmIPBSwACgkQUevqPMjh
pYBjmg//RUzlssNhvaB8m/X6cfZHA03rkQgVhPzUtTGryyge5aT6GqxPfD4+5Vdf
e1vdZJNzt1pIVt4yBYZmTKv2qkyDjJ0TdYJ+r2/neNY3T6IL4oOscPKnp2yn3n5C
N5NJk48fxgXRnnkjBQVFeukaHGEs2F6PbI/z7Dn4on7MiinGBewlPaPRCQUee+i6
eQNQ82tfUMKfgJoaTm71SuZghRUU89scl9V/0/BSkrNNWOuHpxcG/Amq4ap8IxEE
oMEAfhBxKBKqvb3tGDnoljEB8T8RaGpzx0yeice7+3NfqjUw4lE2E7ahbUqFoom5
nJiCbuX5hsYn5GRC/ucNvWka50EInuqs4MFsdGP82v/ruH2O+/V9Dl8JLGfyuc+8
9MSHatRS/3np+M/CZnPJgLS1rutbmWP9hCQ/fs4LzOe8KJboN3R00LXxcNIuK6p5
GV8qthSAKD4rvrjPw26OLUXwZRjpf7hMeOoDZTfWqscIN1E3G3EbCUbQ4EMxwCf2
Qc5DkB30XzHeYK4n/Ee+aNiqhGkI0i9ODSBS7JytEANGWdSQBPAC9n5wW00aln0V
Df/KfCaafZzGEKhdHJTDNzGM8QoCwLvg24jP24VSa1OOz1bOL8hCGxNw/FUS0Ykk
lWw+PYO4/uBx07VeaA2in3zj7mNlwnNNyP2aA3HIRyA2t7LL1BQ=
=h/wV
-----END PGP SIGNATURE-----
next reply other threads:[~2022-02-18 2:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 2:54 Michael Ellerman [this message]
2022-02-18 17:39 ` [GIT PULL] Please pull powerpc/linux.git powerpc-5.17-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=87pmnknauq.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=anders.roxell@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).