public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed

From: will.deacon@arm•com (Will Deacon)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] arm64: fixes for -rc5
Date: Fri, 11 May 2018 18:30:20 +0100	[thread overview]
Message-ID: <20180511173020.GG4954@arm.com> (raw)

Hi Linus,

Please pull these arm64 fixes for -rc5. There's a small memblock accounting
problem when freeing the initrd and a Spectre-v2 mitigation for NVIDIA Denver
CPUs which just requires a match on the CPU ID register.

Thanks,

Will

--->8

The following changes since commit 6da6c0db5316275015e8cc2959f12a17584aeb64:

  Linux v4.17-rc3 (2018-04-29 14:17:42 -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 0583a4ef05987f7e0f3a7bdd3365e5dc36ca306d:

  arm64: capabilities: Add NVIDIA Denver CPU to bp_harden list (2018-05-09 14:28:28 +0100)

----------------------------------------------------------------
arm64 fixes:

- Mitigate Spectre-v2 for NVIDIA Denver CPUs

- Free memblocks corresponding to freed initrd area

----------------------------------------------------------------
CHANDAN VN (1):
      arm64: To remove initrd reserved area entry from memblock

David Gilhooley (2):
      arm64: Add MIDR encoding for NVIDIA CPUs
      arm64: capabilities: Add NVIDIA Denver CPU to bp_harden list

 arch/arm64/include/asm/cputype.h | 6 ++++++
 arch/arm64/kernel/cpu_errata.c   | 1 +
 arch/arm64/mm/init.c             | 4 +++-
 3 files changed, 10 insertions(+), 1 deletion(-)

next             reply	other threads:[~2018-05-11 17:30 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 17:30 Will Deacon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-20 13:06 [GIT PULL] arm64 fixes for -rc5 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-07-10 14:39 [GIT PULL] arm64 fixes " Will Deacon
2020-07-10 16:55 ` pr-tracker-bot
2020-03-06 15:12 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
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=20180511173020.GG4954@arm.com \
    --to=will.deacon@arm$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox