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: merge window fixes for -rc1
Date: Fri, 17 Aug 2018 17:36:42 +0100	[thread overview]
Message-ID: <20180817163641.GC12205@arm.com> (raw)

Hi Linus,

I'm travelling next week and a couple of fixes came in since our main
pull request on Tuesday. Since one of them fixes a boot failure on
Hikey-960, I figured there was no point holding them off until -rc1 is
released, so please consider pulling them beforehand.

Details in the tag.

Cheers,

Will

--->8

The following changes since commit 3c4d9137eefecf273a520d392071ffc9df0a9a7a:

  arm64: alternative: Use true and false for boolean values (2018-08-08 11:20:54 +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 5ad356eabc47d26a92140a0c4b20eba471c10de3:

  arm64: mm: check for upper PAGE_SHIFT bits in pfn_valid() (2018-08-17 10:27:14 +0100)

----------------------------------------------------------------
A couple of arm64 fixes

- Fix boot on Hikey-960 by avoiding an IPI with interrupts disabled
- Fix address truncation in pfn_valid() implementation

----------------------------------------------------------------
Greg Hackmann (1):
      arm64: mm: check for upper PAGE_SHIFT bits in pfn_valid()

Will Deacon (1):
      arm64: Avoid calling stop_machine() when patching jump labels

 arch/arm64/kernel/jump_label.c | 2 +-
 arch/arm64/mm/init.c           | 6 +++++-
 2 files changed, 6 insertions(+), 2 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: merge window fixes for -rc1
Date: Fri, 17 Aug 2018 17:36:42 +0100	[thread overview]
Message-ID: <20180817163641.GC12205@arm.com> (raw)

Hi Linus,

I'm travelling next week and a couple of fixes came in since our main
pull request on Tuesday. Since one of them fixes a boot failure on
Hikey-960, I figured there was no point holding them off until -rc1 is
released, so please consider pulling them beforehand.

Details in the tag.

Cheers,

Will

--->8

The following changes since commit 3c4d9137eefecf273a520d392071ffc9df0a9a7a:

  arm64: alternative: Use true and false for boolean values (2018-08-08 11:20:54 +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 5ad356eabc47d26a92140a0c4b20eba471c10de3:

  arm64: mm: check for upper PAGE_SHIFT bits in pfn_valid() (2018-08-17 10:27:14 +0100)

----------------------------------------------------------------
A couple of arm64 fixes

- Fix boot on Hikey-960 by avoiding an IPI with interrupts disabled
- Fix address truncation in pfn_valid() implementation

----------------------------------------------------------------
Greg Hackmann (1):
      arm64: mm: check for upper PAGE_SHIFT bits in pfn_valid()

Will Deacon (1):
      arm64: Avoid calling stop_machine() when patching jump labels

 arch/arm64/kernel/jump_label.c | 2 +-
 arch/arm64/mm/init.c           | 6 +++++-
 2 files changed, 6 insertions(+), 2 deletions(-)

             reply	other threads:[~2018-08-17 16:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 16:36 Will Deacon [this message]
2018-08-17 16:36 ` [GIT PULL] arm64: merge window fixes for -rc1 Will Deacon
  -- strict thread matches above, loose matches on Subject: below --
2020-06-11 17:34 [GIT PULL] arm64 " Will Deacon
2020-06-11 17:34 ` Will Deacon
2020-06-11 22:00 ` pr-tracker-bot
2020-06-11 22:00   ` pr-tracker-bot

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=20180817163641.GC12205@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.