Linux-ARM-Kernel 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, kernel-team@android.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64 fixes for -rc5
Date: Fri, 10 Jul 2020 15:39:08 +0100	[thread overview]
Message-ID: <20200710143908.GB31036@willie-the-truck> (raw)

Hi Linus,

Please pull this unfortunately large collection of arm64 fixes for -rc5.
Some of this is absolutely trivial, but the alternatives, vDSO and CPU
errata workaround fixes are significant. At least people are finding and
fixing these things, I suppose.

Summary in the tag.

Cheers,

Will

--->8

The following changes since commit 9b23d95c539ebc5d6d6b5d6f20d2d7922384e76e:

  arm64: Add KRYO4XX silver CPU cores to erratum list 1530923 and 1024718 (2020-07-03 16:39:16 +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 5679b28142193a62f6af93249c0477be9f0c669b:

  arm64/alternatives: don't patch up internal branches (2020-07-09 14:57:59 +0100)

----------------------------------------------------------------
arm64 fixes for -rc5

- Fix workaround for CPU erratum #1418040 to disable the compat vDSO

- Fix OOPs when single-stepping with KGDB

- Fix memory attributes for hypervisor device mappings at EL2

- Fix memory leak in PSCI and remove useless variable assignment

- Fix up some comments and asm labels in our entry code

- Fix broken register table formatting in our generated html docs

- Fix missing NULL sentinel in CPU errata workaround list

- Fix patching of branches in alternative instruction sections

----------------------------------------------------------------
Ard Biesheuvel (1):
      arm64/alternatives: don't patch up internal branches

Florian Fainelli (1):
      arm64: Add missing sentinel to erratum_1463225

Gavin Shan (2):
      drivers/firmware/psci: Fix memory leakage in alloc_init_cpu_groups()
      drivers/firmware/psci: Assign @err directly in hotplug_tests()

Kevin Hao (1):
      arm64: entry: Fix the typo in the comment of el1_dbg()

Marc Zyngier (4):
      arm64: Introduce a way to disable the 32bit vdso
      arm64: arch_timer: Allow an workaround descriptor to disable compat vdso
      arm64: arch_timer: Disable the compat vdso for cores affected by ARM64_WORKAROUND_1418040
      arm64: Rework ARM_ERRATUM_1414080 handling

Suzuki K Poulose (1):
      arm64: Documentation: Fix broken table in generated HTML

Wei Li (1):
      arm64: kgdb: Fix single-step exception handling oops

Will Deacon (2):
      KVM: arm64: Fix definition of PAGE_HYP_DEVICE
      arm64: entry: Tidy up block comments and label numbers

 Documentation/arm64/cpu-feature-registers.rst     |  2 +
 arch/arm64/include/asm/arch_timer.h               |  1 +
 arch/arm64/include/asm/pgtable-prot.h             |  2 +-
 arch/arm64/include/asm/vdso/clocksource.h         |  7 ++-
 arch/arm64/include/asm/vdso/compat_gettimeofday.h |  8 +++-
 arch/arm64/kernel/alternative.c                   | 16 +------
 arch/arm64/kernel/cpu_errata.c                    |  1 +
 arch/arm64/kernel/entry-common.c                  |  2 +-
 arch/arm64/kernel/entry.S                         | 52 ++++++++++++++---------
 arch/arm64/kernel/kgdb.c                          |  2 +-
 drivers/clocksource/arm_arch_timer.c              | 11 +++++
 drivers/firmware/psci/psci_checker.c              |  8 ++--
 12 files changed, 68 insertions(+), 44 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2020-07-10 14:40 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 14:39 Will Deacon [this message]
2020-07-10 16:55 ` [GIT PULL] arm64 fixes for -rc5 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-07-24 16:26 Will Deacon
2026-07-24 19:23 ` pr-tracker-bot
2026-03-20 13:06 Will Deacon
2026-03-20 16:25 ` pr-tracker-bot
2025-03-01 21:21 Will Deacon
2025-03-01 21:48 ` pr-tracker-bot
2024-02-16 11:58 Will Deacon
2024-02-16 18:52 ` pr-tracker-bot
2023-10-06  7:56 Will Deacon
2023-10-06 15:15 ` pr-tracker-bot
2023-07-21 11:44 Will Deacon
2023-07-21 11:45 ` Will Deacon
2023-07-21 17:28 ` pr-tracker-bot
2022-09-11 11:37 Will Deacon
2022-09-11 19:36 ` pr-tracker-bot
2021-08-06 13:53 Will Deacon
2021-08-06 18:40 ` Linus Torvalds
2021-08-09 10:52   ` Will Deacon
2021-08-06 18:48 ` pr-tracker-bot
2021-03-25 14:54 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-25 19:13 ` pr-tracker-bot
2020-03-06 15:12 [GIT PULL] arm64 fixes " Will Deacon
2020-03-06 20:55 ` pr-tracker-bot
2019-06-14 15:02 [GIT PULL] arm64: " Will Deacon
2019-06-14 16:20 ` pr-tracker-bot
2019-04-12 16:05 [GIT PULL] arm64 " Will Deacon
2019-04-13 17:40 ` pr-tracker-bot
2019-02-01 17:51 [GIT PULL] arm64: " Will Deacon
2019-02-02  1:00 ` pr-tracker-bot
2018-05-11 17:30 Will Deacon
2017-03-31 17:15 Will Deacon
2016-06-24 11:41 Will Deacon
2016-02-19 16:29 Will Deacon
2015-10-07 14:20 Will Deacon
2015-01-16 17:16 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=20200710143908.GB31036@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 \
    /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