linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: First round of fixes for -rc2
Date: Wed, 22 May 2019 14:11:02 +0100	[thread overview]
Message-ID: <20190522131102.GC7876@fuggles.cambridge.arm.com> (raw)

Hi Linus,

Please pull these arm64 fixes for -rc2. The summary is in the tag.

I was actually planning to send these in during the merge window, which
is why the branch is based on top of the previous arm64 pull rather than
-rc1. Unfortunately, due to various goings on, my ability to send
external email has been patchy (no pun intended) but here we are anyway.

I'll probably send some more fixes in later this week, but based on -rc1
to avoid conflicts.

Cheers,

Will

--->8

The following changes since commit b33f908811b7627015238e0dee9baf2b4c9d720d:

  Merge branch 'for-next/perf' of git://git.kernel.org/pub/scm/linux/kernel/git/will/linux into for-next/core (2019-05-03 10:18:08 +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 7a0a93c51799edc45ee57c6cc1679aa94f1e03d5:

  arm64: vdso: Explicitly add build-id option (2019-05-16 11:45:36 +0100)

----------------------------------------------------------------
First round of arm64 fixes for -rc2

- Fix SPE probe failure when backing auxbuf with high-order pages

- Fix handling of DMA allocations from outside of the vmalloc area

- Fix generation of build-id ELF section for vDSO object

- Disable huge I/O mappings if kernel page table dumping is enabled

- A few other minor fixes (comments, kconfig etc)

----------------------------------------------------------------
Christoph Hellwig (1):
      arm64/iommu: handle non-remapped addresses in ->mmap and ->get_sgtable

Hillf Danton (1):
      arm64: assembler: Update comment above cond_yield_neon() macro

Laura Abbott (1):
      arm64: vdso: Explicitly add build-id option

Mark Rutland (1):
      arm64/mm: Inhibit huge-vmap with ptdump

Will Deacon (2):
      drivers/perf: arm_spe: Don't error on high-order pages for aux buf
      arm64: Print physical address of page table base in show_pte()

Yury Norov (1):
      arm64: don't trash config with compat symbol if COMPAT is disabled

 arch/arm64/Kconfig                 |  2 +-
 arch/arm64/include/asm/assembler.h | 11 +++++------
 arch/arm64/kernel/vdso/Makefile    |  4 ++--
 arch/arm64/mm/dma-mapping.c        | 10 ++++++++++
 arch/arm64/mm/fault.c              |  5 +++--
 arch/arm64/mm/mmu.c                | 11 ++++++++---
 drivers/perf/arm_spe_pmu.c         | 10 +---------
 7 files changed, 30 insertions(+), 23 deletions(-)

             reply	other threads:[~2019-05-22 13:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 13:11 Will Deacon [this message]
2019-05-22 16:00 ` [GIT PULL] arm64: First round of fixes for -rc2 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=20190522131102.GC7876@fuggles.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=catalin.marinas@arm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).