From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
muriloo@linux.ibm.com
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-5.17-5 tag
Date: Sun, 06 Mar 2022 18:51:36 +1100 [thread overview]
Message-ID: <87bkyjo6wn.fsf@mpe.ellerman.id.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull another powerpc fix for 5.17:
The following changes since commit fe663df7825811358531dc2e8a52d9eaa5e3515e:
powerpc/lib/sstep: fix 'ptesync' build error (2022-02-15 22:31:35 +1100)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-5.17-5
for you to fetch changes up to 58dbe9b373df2828d873b1c0e5afc77485b2f376:
powerpc/64s: Fix build failure when CONFIG_PPC_64S_HASH_MMU is not set (2022-03-05 20:42:21 +1100)
- ------------------------------------------------------------------
powerpc fixes for 5.17 #5
Fix build failure when CONFIG_PPC_64S_HASH_MMU is not set.
Thanks to: Murilo Opsfelder Araujo, Erhard F.
- ------------------------------------------------------------------
Murilo Opsfelder Araujo (1):
powerpc/64s: Fix build failure when CONFIG_PPC_64S_HASH_MMU is not set
arch/powerpc/include/asm/book3s/64/mmu.h | 2 +-
arch/powerpc/include/asm/kexec_ranges.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmIkZ+cACgkQUevqPMjh
pYCF1BAAnmZb6JbgLgztefPUyq9mx0q5FqcCqAhj6I+x/8T4qBGawbFpqazW6BIm
i1vHp2Yrj+S86qDQLo33LzO4nKK+EMDhgCAjFpryD8Kla0wDHBYDZy6JMd7LDYao
+j0EBB3w+HOWIUB50fb6EbEgRUFA1gMK4UaOxDRW5dnZCJ7h2qWB5Yev4i1Lzkmb
tPMvfPQYqMjzEcdMt07m7qHG72VxyBUgQbSMhE7VSKjmp9/oNPzxFFBmA0HoX6md
0pwXfXtvnVnMboSTHBYe6Ohk+kdA2P8P7agn/TW0kENP+RM+KePWVOAvAfqPjYCJ
dmqQsmn5ar46tlpPTS834ErDlCNNmfWuNAVILxUt3hQOyHQn4lDDZLR6EDKX22GX
OV9Hth5VPKqkiz8PmGAgcTE+A0s+kGU8DZN9LZefyBLV3Wb5/gHuxQFn8SCX71aE
EtcPJTP7IxZN8epI0b0ZEwM88i6RtFcteAlwYErGe9/UYBJK91zHj4FMWf83BI73
tmJkaVcDDezsbKGuibj3THB5SgzCcp/W5FrPjHWGXbrtYvjGuYp0HKraMGiLimlo
QV3uB/j7qMK0zHBXcypH0P6RrNN3NlaFiSMdl7KrdeWEsaGN8dQ8vKDYo3gJSKF+
lbUkYQV0d6RvHVZvgT11WC9o1SoKH2V5n9OGKNKUmz4RquAbCd8=
=7GLj
-----END PGP SIGNATURE-----
next reply other threads:[~2022-03-06 7:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 7:51 Michael Ellerman [this message]
2022-03-06 20:00 ` [GIT PULL] Please pull powerpc/linux.git powerpc-5.17-5 tag Linus Torvalds
2022-03-06 23:27 ` Michael Ellerman
2022-03-06 20:34 ` 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=87bkyjo6wn.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=muriloo@linux.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