All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
	gregkh@linuxfoundation.org
Subject: [GIT PULL] arm64: fixes for 5.2
Date: Mon, 1 Jul 2019 14:02:12 +0100	[thread overview]
Message-ID: <20190701130212.ifn7d7p2mqvquq6u@willie-the-truck> (raw)

Hi Linus,

When you get a chance, please can you pull these two arm64 fixes for 5.2?
They fix a build failure with the LLVM linker and a module allocation
failure when KASLR is active.

Thanks,

Will

--->8

The following changes since commit 615c48ad8f4275b4d39fa57df68d4015078be201:

  arm64/mm: don't initialize pgd_cache twice (2019-06-18 14:37:28 +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 aa69fb62bea15126e744af2e02acc0d6cf3ed4da:

  arm64/efi: Mark __efistub_stext_offset as an absolute symbol explicitly (2019-06-26 11:40:20 +0100)

----------------------------------------------------------------
arm64 fixes for 5.2

- Fix module allocation when running with KASLR enabled

- Fix broken build due to bug in LLVM linker (ld.lld)

----------------------------------------------------------------
Ard Biesheuvel (1):
      arm64: kaslr: keep modules inside module region when KASAN is enabled

Nathan Chancellor (1):
      arm64/efi: Mark __efistub_stext_offset as an absolute symbol explicitly

 arch/arm64/kernel/image.h  | 6 +++++-
 arch/arm64/kernel/module.c | 8 ++++++--
 2 files changed, 11 insertions(+), 3 deletions(-)

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, gregkh@linuxfoundation.org
Subject: [GIT PULL] arm64: fixes for 5.2
Date: Mon, 1 Jul 2019 14:02:12 +0100	[thread overview]
Message-ID: <20190701130212.ifn7d7p2mqvquq6u@willie-the-truck> (raw)

Hi Linus,

When you get a chance, please can you pull these two arm64 fixes for 5.2?
They fix a build failure with the LLVM linker and a module allocation
failure when KASLR is active.

Thanks,

Will

--->8

The following changes since commit 615c48ad8f4275b4d39fa57df68d4015078be201:

  arm64/mm: don't initialize pgd_cache twice (2019-06-18 14:37:28 +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 aa69fb62bea15126e744af2e02acc0d6cf3ed4da:

  arm64/efi: Mark __efistub_stext_offset as an absolute symbol explicitly (2019-06-26 11:40:20 +0100)

----------------------------------------------------------------
arm64 fixes for 5.2

- Fix module allocation when running with KASLR enabled

- Fix broken build due to bug in LLVM linker (ld.lld)

----------------------------------------------------------------
Ard Biesheuvel (1):
      arm64: kaslr: keep modules inside module region when KASAN is enabled

Nathan Chancellor (1):
      arm64/efi: Mark __efistub_stext_offset as an absolute symbol explicitly

 arch/arm64/kernel/image.h  | 6 +++++-
 arch/arm64/kernel/module.c | 8 ++++++--
 2 files changed, 11 insertions(+), 3 deletions(-)

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

             reply	other threads:[~2019-07-01 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 13:02 Will Deacon [this message]
2019-07-01 13:02 ` [GIT PULL] arm64: fixes for 5.2 Will Deacon
2019-07-03  8:20 ` pr-tracker-bot
2019-07-03  8:20   ` 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=20190701130212.ifn7d7p2mqvquq6u@willie-the-truck \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --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 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.