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-6.12-3 tag
Date: Sun, 06 Oct 2024 18:02:46 +1100 [thread overview]
Message-ID: <87bjzxlnmx.fsf@mail.lhotse> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi Linus,
Please pull some more powerpc fixes for 6.12:
The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:
Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-6.12-3
for you to fetch changes up to 4b058c9f281f5b100efbf665dd5a1a05e1654d6d:
powerpc/vdso: allow r30 in vDSO code generation of getrandom (2024-09-30 19:19:43 +1000)
- ------------------------------------------------------------------
powerpc fixes for 6.12 #3
- Allow r30 to be used in vDSO code generation of getrandom.
Thanks to: Jason A. Donenfeld.
- ------------------------------------------------------------------
Jason A. Donenfeld (1):
powerpc/vdso: allow r30 in vDSO code generation of getrandom
arch/powerpc/kernel/vdso/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQRjvi15rv0TSTaE+SIF0oADX8seIQUCZwI15wAKCRAF0oADX8se
Ia03AP9Wmr2WQ9B2Ei8oQMJBIZkPxkdnqG+K98O3ggFZv8Qz3QD+NgQXIYs+Gvay
5Ql5F5hp1D+KepgXmJJsGVhql2vrMgI=
=vwqi
-----END PGP SIGNATURE-----
next reply other threads:[~2024-10-06 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 7:02 Michael Ellerman [this message]
2024-10-06 19:14 ` [GIT PULL] Please pull powerpc/linux.git powerpc-6.12-3 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=87bjzxlnmx.fsf@mail.lhotse \
--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).