From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com
Subject: [GIT PULL] arm64: fixes for -rc6
Date: Thu, 20 Jun 2019 17:59:16 +0100 [thread overview]
Message-ID: <20190620165916.GB24650@fuggles.cambridge.arm.com> (raw)
Hi Linus,
Please pull these arm64 fixes for -rc6. It's mainly a couple of email
address updates to MAINTAINERS, but we've also fixed a UAPI build issue
with musl libc and an accidental double-initialisation of our pgd_cache
due to a naming conflict with a weak symbol.
There are a couple of outstanding issues that have been reported, but
it doesn't look like they're new and we're still a long way off from
fully debugging them.
Cheers,
Will
--->8
The following changes since commit 41040cf7c5f0f26c368bc5d3016fed3a9ca6dba4:
arm64/sve: Fix missing SVE/FPSIMD endianness conversions (2019-06-13 10:07:19 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes
for you to fetch changes up to 615c48ad8f4275b4d39fa57df68d4015078be201:
arm64/mm: don't initialize pgd_cache twice (2019-06-18 14:37:28 +0100)
----------------------------------------------------------------
arm64 fixes for -rc6
- Fix use of #include in UAPI headers for compatability with musl libc
- Update email addresses in MAINTAINERS
- Fix initialisation of pgd_cache due to name collision with weak symbol
----------------------------------------------------------------
Anisse Astier (2):
arm64: ssbd: explicitly depend on <linux/prctl.h>
arm64/sve: <uapi/asm/ptrace.h> should not depend on <uapi/linux/prctl.h>
Hanjun Guo (1):
MAINTAINERS: Update my email address
Mike Rapoport (1):
arm64/mm: don't initialize pgd_cache twice
Will Deacon (1):
MAINTAINERS: Update my email address to use @kernel.org
.mailmap | 2 ++
MAINTAINERS | 18 +++++++++---------
arch/arm64/include/asm/pgtable.h | 3 +--
arch/arm64/include/uapi/asm/ptrace.h | 8 +++-----
arch/arm64/kernel/ssbd.c | 1 +
5 files changed, 16 insertions(+), 16 deletions(-)
next reply other threads:[~2019-06-20 16:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-20 16:59 Will Deacon [this message]
2019-06-20 19:10 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-11-11 18:07 [GIT PULL] arm64 " Will Deacon
2025-11-11 19:10 ` pr-tracker-bot
2025-07-09 15:08 Will Deacon
2025-07-09 18:37 ` pr-tracker-bot
2024-11-01 11:22 Will Deacon
2024-11-01 18:34 ` pr-tracker-bot
2024-06-28 8:59 Will Deacon
2024-06-28 17:01 ` pr-tracker-bot
2024-02-23 10:25 Will Deacon
2024-02-23 18:44 ` pr-tracker-bot
2023-06-08 20:51 Will Deacon
2023-06-08 21:49 ` pr-tracker-bot
2021-12-15 11:19 Will Deacon
2021-12-15 16:00 ` Catalin Marinas
2021-12-15 18:49 ` Linus Torvalds
2020-11-27 11:40 Will Deacon
2020-11-27 19:19 ` pr-tracker-bot
2020-07-17 15:20 Will Deacon
2020-07-17 23:45 ` pr-tracker-bot
2019-11-01 14:32 [GIT PULL] arm64: Fixes " Will Deacon
2019-11-01 17:10 ` pr-tracker-bot
2019-08-24 12:12 Will Deacon
2019-08-24 18:45 ` pr-tracker-bot
2019-02-08 17:35 [GIT PULL] arm64: fixes " Will Deacon
2019-02-09 0:40 ` pr-tracker-bot
2017-04-07 16:02 Will Deacon
2017-04-11 19:12 ` Jon Masters
2017-04-12 9:14 ` Will Deacon
2017-04-12 10:18 ` Punit Agrawal
2015-10-15 13:38 Will Deacon
2015-01-23 16:44 Will Deacon
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=20190620165916.GB24650@fuggles.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®