public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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,
	npiggin@gmail.com
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-6.1-5 tag
Date: Sun, 20 Nov 2022 12:34:18 +1100	[thread overview]
Message-ID: <87tu2ucsth.fsf@mpe.ellerman.id.au> (raw)

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

Hi Linus,

Please pull another powerpc fix for 6.1:

The following changes since commit 02a771c9a68a9f08cce4ec5e324fb1bc4dce7202:

  powerpc/32: Select ARCH_SPLIT_ARG64 (2022-11-01 15:27:12 +1100)

are available in the git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-6.1-5

for you to fetch changes up to eb761a1760bf30cf64e98ee8d914866e62ec9e8a:

  powerpc: Fix writable sections being moved into the rodata region (2022-11-16 21:37:14 +1100)

- ------------------------------------------------------------------
powerpc fixes for 6.1 #5

 - Fix writable sections being moved into the rodata region.

Thanks to: Nicholas Piggin, Christophe Leroy.

- ------------------------------------------------------------------
Nicholas Piggin (1):
      powerpc: Fix writable sections being moved into the rodata region


 arch/powerpc/kernel/vmlinux.lds.S | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmN5g9sACgkQUevqPMjh
pYAUKQ/+II2IDXsGIAf7Nh6Bu7+VbvKj7RPKABPfGWwyW1TQ2AMe0MSjRBc8CMgk
NWUlZNUkXfonS0WCNET/tgfzYU4qYP0JJDLlxvh790LuaAJ7VVw0a9phPYm4YptM
3mlGo6jj9dU3Xmb/TuJCyxHhaBIpdcaEzLYRUFT8vlMl++U65tJN+q7YMBlJ0Q9e
4HIL1yxeek6Bd6wxqgsS/L8J8s52A3iQBTAUHNQaSqZTQKjLxWS9u3oY18S/1+u2
8zLkyTHFWM8EClDmU8IEHPNonVBjWbTUmZji9Akp/2osh2uQlYtpE7eCR5VNsYtn
Tkuv0lQLFNOWraOl97DdKEfJJxX2sZPt+0I1UhywN6wabHY0UiZjHm/3nUdYMtAa
tEsKoj4m+gydD9aM1q+UkFGd7gsXWf8GqQ22TEd73HoE0nL2Prr18bNGyX0KYzH4
BPHYaoOe2pQpaix83Cod6VkrKdShBpUCw9hIF+Tj0nWXNgBNJP+UnBj5157DOIqO
WNFUkQKNYuebhO453zhBQA7EEO5GNjpbXrxsuLKz8A4m9Wlu3MxX1gHxp5nJbkif
D86ifPZaaOMixPDAHygzihsXpTKQ0fnhRp8tguRBwwoN5MTOZp0HNsAhzEBrKTta
hPar+QyWwSXjcH2SC7BoH0sIPDwdBCkwthh4kvgATr+fn2EuKi0=
=mxZu
-----END PGP SIGNATURE-----

             reply	other threads:[~2022-11-20  1:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20  1:34 Michael Ellerman [this message]
2022-11-20 18:52 ` [GIT PULL] Please pull powerpc/linux.git powerpc-6.1-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=87tu2ucsth.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.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