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 -rc2
Date: Fri, 31 Aug 2018 17:12:13 +0100	[thread overview]
Message-ID: <20180831161213.GH30626@arm.com> (raw)

Hi Linus,

A few arm64 fixes came in this week, specifically fixing some nasty
truncation of return values from firmware calls and resolving a VM_BUG_ON
due to accessing uninitialised struct pages corresponding to NOMAP pages.
Details in the tag.

Please pull, thanks.

Will

--->8

The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:

  Linux 4.19-rc1 (2018-08-26 14:11:59 -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 f52bb98f5aded4c43e52f5ce19fb83f7261e9e73:

  arm64: mm: always enable CONFIG_HOLES_IN_ZONE (2018-08-31 11:06:45 +0100)

----------------------------------------------------------------
A handful of arm64 fixes

- Fix typos in SVE documentation
- Fix type-checking and implicit truncation for SMCCC calls
- Force CONFIG_HOLES_IN_ZONE=y so that SLAB doesn't fall over NOMAP regions

----------------------------------------------------------------
James Morse (1):
      arm64: mm: always enable CONFIG_HOLES_IN_ZONE

Julien Grall (1):
      Documentation/arm64/sve: Couple of improvements and typos

Marc Zyngier (2):
      arm/arm64: smccc-1.1: Make return values unsigned long
      arm/arm64: smccc-1.1: Handle function result as parameters

 Documentation/arm64/sve.txt |  4 ++--
 arch/arm64/Kconfig          |  1 -
 include/linux/arm-smccc.h   | 38 ++++++++++++++++++++++++--------------
 3 files changed, 26 insertions(+), 17 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 -rc2
Date: Fri, 31 Aug 2018 17:12:13 +0100	[thread overview]
Message-ID: <20180831161213.GH30626@arm.com> (raw)

Hi Linus,

A few arm64 fixes came in this week, specifically fixing some nasty
truncation of return values from firmware calls and resolving a VM_BUG_ON
due to accessing uninitialised struct pages corresponding to NOMAP pages.
Details in the tag.

Please pull, thanks.

Will

--->8

The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:

  Linux 4.19-rc1 (2018-08-26 14:11:59 -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 f52bb98f5aded4c43e52f5ce19fb83f7261e9e73:

  arm64: mm: always enable CONFIG_HOLES_IN_ZONE (2018-08-31 11:06:45 +0100)

----------------------------------------------------------------
A handful of arm64 fixes

- Fix typos in SVE documentation
- Fix type-checking and implicit truncation for SMCCC calls
- Force CONFIG_HOLES_IN_ZONE=y so that SLAB doesn't fall over NOMAP regions

----------------------------------------------------------------
James Morse (1):
      arm64: mm: always enable CONFIG_HOLES_IN_ZONE

Julien Grall (1):
      Documentation/arm64/sve: Couple of improvements and typos

Marc Zyngier (2):
      arm/arm64: smccc-1.1: Make return values unsigned long
      arm/arm64: smccc-1.1: Handle function result as parameters

 Documentation/arm64/sve.txt |  4 ++--
 arch/arm64/Kconfig          |  1 -
 include/linux/arm-smccc.h   | 38 ++++++++++++++++++++++++--------------
 3 files changed, 26 insertions(+), 17 deletions(-)

             reply	other threads:[~2018-08-31 16:12 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31 16:12 Will Deacon [this message]
2018-08-31 16:12 ` [GIT PULL] arm64: fixes for -rc2 Will Deacon
  -- strict thread matches above, loose matches on Subject: below --
2026-02-27 21:20 [GIT PULL] arm64 " Will Deacon
2026-02-27 21:46 ` pr-tracker-bot
2022-04-08 16:29 Will Deacon
2022-04-08 16:29 ` Will Deacon
2022-04-08 17:46 ` pr-tracker-bot
2022-04-08 17:46   ` pr-tracker-bot
2021-07-16 14:53 Will Deacon
2021-07-16 14:53 ` Will Deacon
2021-07-17  2:12 ` pr-tracker-bot
2021-07-17  2:12   ` pr-tracker-bot
2020-10-30 17:05 Will Deacon
2020-10-30 17:05 ` Will Deacon
2020-10-30 20:29 ` pr-tracker-bot
2020-10-30 20:29   ` pr-tracker-bot
2020-06-19 12:43 Will Deacon
2020-06-19 12:43 ` Will Deacon
2020-06-19 19:30 ` pr-tracker-bot
2020-06-19 19:30   ` pr-tracker-bot
2020-02-13 17:10 Will Deacon
2020-02-13 17:10 ` Will Deacon
2020-02-13 22:40 ` pr-tracker-bot
2020-02-13 22:40   ` pr-tracker-bot
2019-07-26 13:12 [GIT PULL] arm64: " Will Deacon
2019-07-26 13:12 ` Will Deacon
2019-07-26 18:25 ` pr-tracker-bot
2019-07-26 18:25   ` pr-tracker-bot
2019-01-11 18:20 Will Deacon
2019-01-11 18:20 ` Will Deacon
2019-01-11 20:40 ` pr-tracker-bot
2019-01-11 20:40   ` pr-tracker-bot
2017-12-01 18:23 Will Deacon
2017-12-01 18:23 ` Will Deacon
2016-10-20 17:14 Will Deacon
2016-10-20 17:14 ` Will Deacon
2016-06-03 15:37 Will Deacon
2016-06-03 15:37 ` Will Deacon
2016-04-01 15:15 Will Deacon
2016-04-01 15:15 ` Will Deacon
2016-01-27 18:45 Will Deacon
2016-01-27 18:45 ` Will Deacon
2015-09-17 14:04 Will Deacon
2015-09-17 14:04 ` 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=20180831161213.GH30626@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.