LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc3
Date: Fri, 6 Nov 2020 13:20:35 +0000	[thread overview]
Message-ID: <20201106132035.GA10755@willie-the-truck> (raw)

Hi Linus,

Here's the weekly batch of fixes for arm64. Not an awful lot here, but
there are still a few unresolved issues relating to CPU hotplug, RCU and
IRQ tracing that I hope to queue fixes for next week.

In the meantime, there's a summary for this lot in the tag.

Cheers,

Will

--->8

The following changes since commit ec9d78070de986ecf581ea204fd322af4d2477ec:

  arm64: Change .weak to SYM_FUNC_START_WEAK_PI for arch/arm64/lib/mem*.S (2020-10-30 08:32:31 +0000)

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 108aa503657ee2fe8aa071dc620d96372c252ecd:

  arm64: kexec_file: try more regions if loading segments fails (2020-11-05 21:48:05 +0000)

----------------------------------------------------------------
arm64 fixes for -rc3

- Fix early use of kprobes

- Fix kernel placement in kexec_file_load()

- Bump maximum number of NUMA nodes

----------------------------------------------------------------
Benjamin Gwin (1):
      arm64: kexec_file: try more regions if loading segments fails

Jean-Philippe Brucker (1):
      arm64: kprobes: Use BRK instead of single-step when executing instructions out-of-line

Vanshidhar Konda (1):
      arm64: NUMA: Kconfig: Increase NODES_SHIFT to 4

 arch/arm64/Kconfig                      |  2 +-
 arch/arm64/include/asm/brk-imm.h        |  2 +
 arch/arm64/include/asm/debug-monitors.h |  1 +
 arch/arm64/include/asm/kprobes.h        |  2 +-
 arch/arm64/kernel/kexec_image.c         | 41 +++++++++++++++-----
 arch/arm64/kernel/machine_kexec_file.c  |  9 ++++-
 arch/arm64/kernel/probes/kprobes.c      | 69 +++++++++++----------------------
 7 files changed, 67 insertions(+), 59 deletions(-)

             reply	other threads:[~2020-11-06 13:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 13:20 Will Deacon [this message]
2020-11-06 21:13 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2021-11-26 13:22 Will Deacon
2021-11-26 18:35 ` pr-tracker-bot
2021-07-22 15:55 Will Deacon
2021-07-22 18:00 ` pr-tracker-bot
2021-03-12 13:34 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-12 20:03 ` pr-tracker-bot
2020-06-26 13:21 [GIT PULL] arm64 fixes " Will Deacon
2020-06-27 16:00 ` pr-tracker-bot
2020-02-21 16:01 Will Deacon
2020-02-22  0:07 ` Linus Torvalds
2020-02-22  0:15 ` pr-tracker-bot
2019-10-09 13:30 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-09 19:30 ` pr-tracker-bot
2019-05-30 16:11 [GIT PULL] arm64: fixes " Will Deacon
2019-05-31  4:25 ` pr-tracker-bot
2019-01-20  0:04 Will Deacon
2019-01-20  3:29 ` Linus Torvalds
2019-01-20  4:00 ` pr-tracker-bot
2018-04-27 16:23 Will Deacon
2017-12-07 17:58 Will Deacon
2016-10-28 16:01 Will Deacon
2016-02-04 18:49 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=20201106132035.GA10755@willie-the-truck \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [GIT PULL] arm64 fixes for -rc3' \
    /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

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).