LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
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
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-5.17-6 tag
Date: Fri, 11 Mar 2022 17:03:15 +1100	[thread overview]
Message-ID: <874k45m3fg.fsf@mpe.ellerman.id.au> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Linus,

Please pull one more powerpc fix for 5.17:

The following changes since commit 58dbe9b373df2828d873b1c0e5afc77485b2f376:

  powerpc/64s: Fix build failure when CONFIG_PPC_64S_HASH_MMU is not set (2022-03-05 20:42:21 +1100)

are available in the git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-5.17-6

for you to fetch changes up to 48015b632f770c401f3816f144499a39f2884677:

  powerpc: Fix STACKTRACE=n build (2022-03-07 10:26:20 +1100)

- ------------------------------------------------------------------
powerpc fixes for 5.17 #6

Fix STACKTRACE=n build, in particular for skiroot_defconfig.

- ------------------------------------------------------------------
Michael Ellerman (1):
      powerpc: Fix STACKTRACE=n build


 arch/powerpc/include/asm/nmi.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmIq5cAACgkQUevqPMjh
pYAJhw//WqcG+Qv+W5YD9KMiH78CTDm9bsLejRJOy3x/Rbn5Fs2/KKdcYPcpe5gE
nJ87W2w2li2YpEBe3ClbAXFQCNswH8cnj3++HLaGFp4bmM3F96JCEuh1GghlvQ4v
e6EUD0qYEmlFRAvey7bfu5MsNLGadpXob4f+xMoffRHr9rhzsShV4b7pAblUggIi
/ajO+GEvIk7kSB7DCGEq8swfoT0mWb0bD2wAhNoz4nbOENaGp7O26Va6vt/l+qHn
aXFESbaYKKBxYTicuLywQWKqL5j/XaHDz19KkKOljYElsLTZ78i4y1mvIHLRJtHA
NxSAPXBZgOyw7/mQJEYP+ABr0ki+QIpykTLeDxL+XSOtOVYEJW8eQiBHbzxrqSCs
7UEyunNG9Y2WfLPpE+lo4QEEeOp+QiJsla3iJjQAMJjI2M8x6QtWkDJlZ+LSfUa0
mNPnHDt8mlAj1R7zpXLNt0gokgPub4lSBb1V2tEu816gEUVJVgqq63GGynB+ET9K
O/3UlU7jFaQzASw4TUgq1HBE8Zs3NC09GbkUzDoo2cqeZDOPDbb0ieJcy+VzDNiq
bAcRwjXB7LKir59G38Mdo2lMALJUXr+jtz10a+zTnA48KAVbf5ZgEwXHejR0Y/nv
af8B1MyWLjeUWAY2CDSSoOres2qE1phjBVZ4eBSk9VLqd+KtXf8=
=KPHf
-----END PGP SIGNATURE-----

             reply	other threads:[~2022-03-11  6:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  6:03 Michael Ellerman [this message]
2022-03-11 20:44 ` [GIT PULL] Please pull powerpc/linux.git powerpc-5.17-6 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=874k45m3fg.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --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