From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jason@zx2c4.com, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-5.5-5 tag
Date: Fri, 03 Jan 2020 21:57:51 +1100 [thread overview]
Message-ID: <87k168lscw.fsf@mpe.ellerman.id.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull two more powerpc fixes for 5.5:
The following changes since commit 46cf053efec6a3a5f343fead837777efe8252a46:
Linux 5.5-rc3 (2019-12-22 17:02:23 -0800)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-5.5-5
for you to fetch changes up to 6da3eced8c5f3b03340b0c395bacd552c4d52411:
powerpc/spinlocks: Include correct header for static key (2019-12-30 21:20:41 +1100)
- ------------------------------------------------------------------
powerpc fixes for 5.5 #5
One commit to fix a build error when CONFIG_JUMP_LABEL=n, introduced by our
recent fix to is_shared_processor().
A commit marking some SLB related functions as notrace, as tracing them triggers
warnings.
Thanks to:
Jason A. Donenfeld.
- ------------------------------------------------------------------
Jason A. Donenfeld (1):
powerpc/spinlocks: Include correct header for static key
Michael Ellerman (1):
powerpc/mm: Mark get_slice_psize() & slice_addr_is_low() as notrace
arch/powerpc/include/asm/spinlock.h | 1 +
arch/powerpc/mm/slice.c | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAl4PHf0ACgkQUevqPMjh
pYD6QxAAshIxGnQ7CfaqbjGRFgXCEEcOhJfR6+D/Kph43vzV5w4v/j0lk2mlydua
eWL1MGvbby1K5rRtNyFJm8+6bScYHxo/GSdsCJ+8UNMt6hTYqlzjn3IqQs0pWQKO
2kJu8/2TpUweemXDQSxWR9NqYuhj9TIKxlk6swdHBfUG/RvQOv+hRow1dPS1QzwG
Euu30QiezEvf2wq7OXbeAub82k243FrRDp3+dMfsXAcYxLlmCDJCQgh91uVIA3yh
PF8EuYbB8sqkJkH5wE2QT6cgssBwthrC9/J5/fVZnnyj9ObRJKt5sPMQ7WXG19D7
TcsXLkHZiwhnas2j7Ze9HFJ7R99lPSy182w8VoSCHjyPB72O3EYVS+7IwvcfnwEe
fBmTQUnR3ToByRig3TaErUZBSn2CSm3mmJTlXP38NOREExJijh92yfSeTlE+cdWD
1B7KhrQlsZ+4cMTX5v3aJXlx02zbghFF7Sbdll7qgjPcDGc+cOTX6UkDmMGLwCN1
0N78mX6YagjYf4Umh29uwwBJ7iXpVzHiSwqoZ79QVVUhAvU2TSvqUthCQZPLLcyy
ssT2WQ3xiCvwS33O5N6arA/1vxB4deUW7ZQbOzPo4tcKDKrF52LnfgWtdJKai877
RRD7jkKxBU0MPcZ4Ohamie/h25gAWDipbScrX8rlXh2zmoH/zB0=
=W3Ow
-----END PGP SIGNATURE-----
next reply other threads:[~2020-01-03 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 10:57 Michael Ellerman [this message]
2020-01-03 19:25 ` [GIT PULL] Please pull powerpc/linux.git powerpc-5.5-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=87k168lscw.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=Jason@zx2c4.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;
as well as URLs for NNTP newsgroup(s).