All of lore.kernel.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 -rc7
Date: Fri, 27 Jul 2018 12:51:34 +0100	[thread overview]
Message-ID: <20180727115133.GD25592@arm.com> (raw)

Hi Linus,

Inevitably, after saying that I hoped we would be done on the fixes front,
a couple of issues have cropped up over the last week. Next time I'll stay
schtum.

As usual, details are in the tag, but we've fixed an over-eager BUILD_BUG_ON()
which Arnd ran into with arndconfig, as well as ensuring that KPTI really
is disabled on Thunder-X1, where the cure is worse than the disease (this
regressed when we reworked the heterogeneous CPU feature checking).

Please pull.

Thanks,

Will

--->8

The following changes since commit d72e90f33aa4709ebecc5005562f52335e106a60:

  Linux 4.18-rc6 (2018-07-22 14:12:20 -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 7b0eb6b41a08fa1fa0d04b1c53becd62b5fbfaee:

  arm64: fix vmemmap BUILD_BUG_ON() triggering on !vmemmap setups (2018-07-25 13:32:30 +0100)

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

- Fix disabling of kpti on Thunder-X machines

- Fix premature BUILD_BUG_ON() found with randconfig

----------------------------------------------------------------
Dirk Mueller (1):
      arm64: Check for errata before evaluating cpu features

Johannes Weiner (1):
      arm64: fix vmemmap BUILD_BUG_ON() triggering on !vmemmap setups

 arch/arm64/kernel/cpufeature.c | 4 ++--
 arch/arm64/mm/init.c           | 4 +++-
 2 files changed, 5 insertions(+), 3 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
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 -rc7
Date: Fri, 27 Jul 2018 12:51:34 +0100	[thread overview]
Message-ID: <20180727115133.GD25592@arm.com> (raw)

Hi Linus,

Inevitably, after saying that I hoped we would be done on the fixes front,
a couple of issues have cropped up over the last week. Next time I'll stay
schtum.

As usual, details are in the tag, but we've fixed an over-eager BUILD_BUG_ON()
which Arnd ran into with arndconfig, as well as ensuring that KPTI really
is disabled on Thunder-X1, where the cure is worse than the disease (this
regressed when we reworked the heterogeneous CPU feature checking).

Please pull.

Thanks,

Will

--->8

The following changes since commit d72e90f33aa4709ebecc5005562f52335e106a60:

  Linux 4.18-rc6 (2018-07-22 14:12:20 -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 7b0eb6b41a08fa1fa0d04b1c53becd62b5fbfaee:

  arm64: fix vmemmap BUILD_BUG_ON() triggering on !vmemmap setups (2018-07-25 13:32:30 +0100)

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

- Fix disabling of kpti on Thunder-X machines

- Fix premature BUILD_BUG_ON() found with randconfig

----------------------------------------------------------------
Dirk Mueller (1):
      arm64: Check for errata before evaluating cpu features

Johannes Weiner (1):
      arm64: fix vmemmap BUILD_BUG_ON() triggering on !vmemmap setups

 arch/arm64/kernel/cpufeature.c | 4 ++--
 arch/arm64/mm/init.c           | 4 +++-
 2 files changed, 5 insertions(+), 3 deletions(-)

             reply	other threads:[~2018-07-27 11:51 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-27 11:51 Will Deacon [this message]
2018-07-27 11:51 ` [GIT PULL] arm64: fixes for -rc7 Will Deacon
  -- strict thread matches above, loose matches on Subject: below --
2025-03-14 16:04 [GIT PULL] arm64 " Will Deacon
2025-03-14 20:34 ` Linus Torvalds
2025-03-17 16:00   ` Will Deacon
2025-03-18 11:43     ` Will Deacon
2025-03-18 11:46     ` Marc Zyngier
2025-03-14 21:03 ` pr-tracker-bot
2024-11-08 11:57 Will Deacon
2024-11-08 17:39 ` pr-tracker-bot
2022-09-23 18:28 Will Deacon
2022-09-23 18:28 ` Will Deacon
2022-09-23 22:43 ` Linus Torvalds
2022-09-23 22:43   ` Linus Torvalds
2022-09-28 10:46   ` Mark Rutland
2022-09-28 10:46     ` Mark Rutland
2022-09-23 22:53 ` pr-tracker-bot
2022-09-23 22:53   ` pr-tracker-bot
2022-05-13 16:52 Will Deacon
2022-05-13 16:52 ` Will Deacon
2022-05-13 17:30 ` pr-tracker-bot
2022-05-13 17:30   ` pr-tracker-bot
2021-08-20  8:53 Will Deacon
2021-08-20  8:53 ` Will Deacon
2021-08-20 20:09 ` pr-tracker-bot
2021-08-20 20:09   ` pr-tracker-bot
2020-12-02 17:17 Will Deacon
2020-12-02 17:17 ` Will Deacon
2020-12-02 20:48 ` pr-tracker-bot
2020-12-02 20:48   ` pr-tracker-bot
2020-03-20 15:35 Will Deacon
2020-03-20 15:35 ` Will Deacon
2020-03-20 17:15 ` pr-tracker-bot
2020-03-20 17:15   ` pr-tracker-bot
2019-08-28 17:32 [GIT PULL] arm64: Fixes " Will Deacon
2019-08-28 17:32 ` Will Deacon
2019-08-28 17:32 ` Will Deacon
2019-08-28 17:45 ` pr-tracker-bot
2019-08-28 17:45   ` pr-tracker-bot
2019-08-28 17:45   ` pr-tracker-bot
2018-05-25 16:04 [GIT PULL] arm64: fixes " Will Deacon
2018-05-25 16:04 ` Will Deacon
2016-07-08 14:49 Will Deacon
2016-07-08 14: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=20180727115133.GD25592@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.