From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com
Subject: [GIT PULL] arm64: fixes for -rc4
Date: Fri, 14 Sep 2018 17:19:08 +0100 [thread overview]
Message-ID: <20180914161908.GF6236@arm.com> (raw)
Hi Linus,
The trickle of arm64 fixes continues to come in. Nothing that's the end
of the world, but we've got a fix for PCI IO port accesses, an accidental
naked "asm goto" and a fix to the vmcoreinfo PT_NOTE merged this time
around which we'd like to get sorted before it becomes ABI.
Details in the tag, but please pull.
Thanks,
Will
--->8
The following changes since commit 11da3a7f84f19c26da6f86af878298694ede0804:
Linux 4.19-rc3 (2018-09-09 17:26:43 -0700)
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 500dd232449e7c07500e713dc6970aa713f8e4f1:
asm-generic: io: Fix ioport_map() for !CONFIG_GENERIC_IOMAP && CONFIG_INDIRECT_PIO (2018-09-14 09:49:21 +0100)
----------------------------------------------------------------
arm64 fixes
- Fix ioport_map() mapping the wrong physical address for some I/O BARs
- Remove direct use of "asm goto", since some compilers don't like that
- Ensure kimage_voffset is always present in vmcoreinfo PT_NOTE
----------------------------------------------------------------
Andrew Murray (1):
asm-generic: io: Fix ioport_map() for !CONFIG_GENERIC_IOMAP && CONFIG_INDIRECT_PIO
James Morse (1):
arm64: kernel: arch_crash_save_vmcoreinfo() should depend on CONFIG_CRASH_CORE
Miguel Ojeda (1):
arm64: jump_label.h: use asm_volatile_goto macro instead of "asm goto"
arch/arm64/include/asm/jump_label.h | 4 ++--
arch/arm64/kernel/Makefile | 1 +
arch/arm64/kernel/crash_core.c | 19 +++++++++++++++++++
arch/arm64/kernel/machine_kexec.c | 11 -----------
include/asm-generic/io.h | 3 ++-
5 files changed, 24 insertions(+), 14 deletions(-)
create mode 100644 arch/arm64/kernel/crash_core.c
next reply other threads:[~2018-09-14 16:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 16:19 Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 10:29 [GIT PULL] arm64 fixes for -rc4 Will Deacon
2023-01-13 13:58 ` pr-tracker-bot
2022-09-02 11:12 Will Deacon
2022-09-02 18:30 ` pr-tracker-bot
2022-04-22 11:20 Will Deacon
2022-04-22 21:19 ` pr-tracker-bot
2021-12-03 13:19 Will Deacon
2021-12-03 18:53 ` pr-tracker-bot
2020-11-13 12:39 GIT " Will Deacon
2020-11-13 12:44 ` [GIT " Will Deacon
2020-11-13 17:25 ` Linus Torvalds
2020-07-04 13:05 Will Deacon
2020-07-05 17:35 ` pr-tracker-bot
2019-10-17 23:43 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-18 0:06 ` Linus Torvalds
2019-10-18 17:41 ` Will Deacon
2019-10-18 19:17 ` Linus Torvalds
2019-10-21 6:46 ` Ingo Molnar
2019-10-21 11:45 ` Linus Torvalds
2019-10-22 8:16 ` Uwe Kleine-König
2019-10-18 0:15 ` pr-tracker-bot
2019-10-18 20:09 ` Jayachandran Chandrasekharan Nair
2019-06-07 15:13 [GIT PULL] arm64: fixes " Will Deacon
2019-06-07 16:45 ` pr-tracker-bot
2019-04-05 17:17 [GIT PULL] arm64 " Catalin Marinas
2019-04-05 23:50 ` pr-tracker-bot
2017-12-15 18:31 [GIT PULL] arm64: " Will Deacon
2017-08-04 18:32 Will Deacon
2016-06-17 17:07 Will Deacon
2015-05-14 15:48 Will Deacon
2015-01-09 15:22 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=20180914161908.GF6236@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;
as well as URLs for NNTP newsgroup(s).