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
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-6.3-2 tag
Date: Sat, 04 Mar 2023 23:11:29 +1100 [thread overview]
Message-ID: <87v8jg1zta.fsf@mpe.ellerman.id.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull a few powerpc fixes for 6.3:
The following changes since commit d0a32f5520a33e7f2ace396db6913625e0d29544:
Merge tag 'powerpc-6.3-1' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux (2023-02-25 11:00:06 -0800)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-6.3-2
for you to fetch changes up to f8b2336f15f3bc30e37ce5c052cde5b6319bb6df:
powerpc: Avoid dead code/data elimination when using recordmcount (2023-02-28 14:32:34 +1100)
- ------------------------------------------------------------------
powerpc fixes for 6.3 #2
- Drop orphaned VAS MAINTAINERS entry.
- Fix build errors with clang and KCSAN.
- Avoid build errors seen with LD_DEAD_CODE_DATA_ELIMINATION & recordmcount.
Thanks to: Nathan Chancellor
- ------------------------------------------------------------------
Michael Ellerman (3):
powerpc: Drop orphaned VAS MAINTAINERS entry
powerpc/vmlinux.lds: Add .text.asan/tsan sections
powerpc: Avoid dead code/data elimination when using recordmcount
MAINTAINERS | 7 -------
arch/powerpc/Kconfig | 2 +-
arch/powerpc/kernel/vmlinux.lds.S | 1 +
3 files changed, 2 insertions(+), 8 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmQDNRIACgkQUevqPMjh
pYBhOg/+NsVj0eyKjVphxmu0dxIb5Qb262EzDcryuxRP56+kk4Q3BvUYrzYB/0mh
xauoqa+ui4Dn9oar+F5v5wyGmR0A16SebUs2bqfjKvjsvHAlsSxxNlL7jRjCdKEZ
yl23e/0YmEGEpUuxy7mxRwzhwobxO9K4JT/ysqUfxR8PNrTbGk+pT6Vo0lYyBDmD
N4jx9i0jxwPR/gxbyOODbXekKu9RysojPUCKjAX7uHq1qO1aefE+1Ajn+mhZsmOI
hi5yaCv2+FUgteCsaCy1eC8pBVmRzY6A/eDGV6ia0Lrs9si+UvqqSAmOsRP0a0lp
r/8RoUFj0T7rJ7PUeZjWxz3l5s+IY+RLW5/a56te9fscsk5gYS9EKZOJhTdjSBo2
9NLySoaBvpHJmcxShkuN/b88NmQwmTq0DkcyggEXsdU85HBhqqx8Fd+5H7sgJ2aN
wK5tOUyo5mkZSK7VBB1m9OG66n4YYrh9glUIda90tNRHDLTGjyKTXKatW9WgUsZH
ufAaZZYGF2NV98c4IrWQqqmYaXQZ4wXlwmBEP9ionPU7GZOkCls7A8pAI42hExh4
Dsd8az78aFcHnJxy2w9845N9Iea1ef2HoDEYvSWIjmkmeCDCueLWusnqWxXG+1zE
LSBHDK+OkjudX0vvnwuL0Y1V9EawoPkI7618cdocIbOs2CDagV8=
=6Vrj
-----END PGP SIGNATURE-----
next reply other threads:[~2023-03-04 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 12:11 Michael Ellerman [this message]
2023-03-04 20:58 ` 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=87v8jg1zta.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
all inboxes | Powered by JetHome®