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,
	naveen@kernel.org
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-6.7-4 tag
Date: Sun, 10 Dec 2023 11:29:22 +1100	[thread overview]
Message-ID: <87sf4aew7x.fsf@mail.lhotse> (raw)

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

Hi Linus,

Please pull some more powerpc fixes for 6.7:

The following changes since commit dc158d23b33df9033bcc8e7117e8591dd2f9d125:

  KVM: PPC: Book3S HV: Fix KVM_RUN clobbering FP/VEC user registers (2023-11-29 22:24:21 +1100)

are available in the git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-6.7-4

for you to fetch changes up to 4b3338aaa74d7d4ec5b6734dc298f0db94ec83d2:

  powerpc/ftrace: Fix stack teardown in ftrace_no_trace (2023-12-05 14:14:12 +1100)

- ------------------------------------------------------------------
powerpc fixes for 6.7 #4

 - Fix stack teardown in ftrace_no_trace, seen as crashes doing CPU hotplug
   while ftrace is active.

Thanks to: Naveen N Rao

- ------------------------------------------------------------------
Naveen N Rao (1):
      powerpc/ftrace: Fix stack teardown in ftrace_no_trace


 arch/powerpc/kernel/trace/ftrace_entry.S | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmV1BNYACgkQUevqPMjh
pYAI2RAAhz0DW42CARKjsiQ/iyDVphkYwuXMMlX6DCSFPBPFZMPkI+wPzwbQDASg
ZW9p3NfxGa68szbKKSqK7RSYjHUAVlff8S4QyqNlnJzEwmErz6dhKa27vgGmE+k/
bgMTJO5qKFIt2WQ/xdvHlFUCzVxa7exxhLvR1fGkYnpENSgZrroq7pI0SuM92pnK
UDpoUeadXNKtwrP4yowdYTrGd0ciMdV2lQDXjG25Z9neW3eX4cT/D6FZLckS61wt
8eVmOlhoElmgLNnz7tsUCrfM02z3/nsU/dRx/jGYMIzlSIc7CNDSC6vVlIjGqoHu
4a/jhTL7OHQcamGo38GsmWenetqvJe+IJj6y5wcykA8z9Y231sUAdbAKbzw73t2k
Gb6wys82twpf8YbakGdzR0rM3aT5oE52ZRsMcoXDWFK7Q12H/euh/h32TmLISknK
tbsIROx/fLB8j8b+6R7Y1+7Kh5bvhckyoJqqjkGzUZMSI8QufEGOwfAnHJhD058x
HYSFJmqioCtwOk5gTe0HRQzTsHU8xQfN+HiLlOO4e7NhJAP3LBGVcx9e4Gbr9j/1
emq4hjB7cO1kBJdjpM0sQt2M2dgAuNzcUimkLqewy/swcR9KQV2NyjnU+teAJK0+
FEqMVVnGd24PdMTjr9fAzC6p0995vxFgWYzXJlwDVPY22AyAjfE=
=VOa0
-----END PGP SIGNATURE-----

             reply	other threads:[~2023-12-10  0:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-10  0:29 Michael Ellerman [this message]
2023-12-10  3:39 ` [GIT PULL] Please pull powerpc/linux.git powerpc-6.7-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=87sf4aew7x.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=naveen@kernel.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