linux-arm-kernel.lists.infradead.org archive mirror
 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, 1 Apr 2016 16:15:23 +0100	[thread overview]
Message-ID: <20160401151521.GA3991@arm.com> (raw)

Hi Linus,

Here are three arm64 patches for -rc2. One of them fixes a nasty code
patching problem for big-endian systems, whilst the other two address
some issues remaining after the merge window. Specifically, cleaning up
after the KVM PMU work and sweeping up some defconfig updates that were
missed, which includes squashing a Kconfig warning from duplicate
definitions of MMC_BLOCK_MINORS.

We're debugging a couple of other issues at the moment, but the wheels
don't appear to have fallen off yet.

Please pull.

Will

--->8

The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:

  Linux 4.6-rc1 (2016-03-26 16:03:24 -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 431597bb95560c975221c0394c442723d7a21f2d:

  arm64: defconfig: updates for 4.6 (2016-03-29 16:56:00 +0100)

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

- Fix oops when patching in alternative sequences on big-endian CPUs
- Reconcile asm/perf_event.h after merge window fallout with KVM ARM
- Defconfig updates

----------------------------------------------------------------
James Morse (1):
      arm64: opcodes.h: Add arm big-endian config options before including arm header

Shannon Zhao (1):
      arm64: perf: Move PMU register related defines to asm/perf_event.h

Will Deacon (1):
      arm64: defconfig: updates for 4.6

 arch/arm64/configs/defconfig            | 28 +++++++++----
 arch/arm64/include/asm/kvm_host.h       |  1 -
 arch/arm64/include/asm/kvm_hyp.h        |  1 -
 arch/arm64/include/asm/kvm_perf_event.h | 68 -------------------------------
 arch/arm64/include/asm/opcodes.h        |  4 ++
 arch/arm64/include/asm/perf_event.h     | 47 +++++++++++++++++++++
 arch/arm64/kernel/perf_event.c          | 72 +++++++++------------------------
 7 files changed, 90 insertions(+), 131 deletions(-)
 delete mode 100644 arch/arm64/include/asm/kvm_perf_event.h

             reply	other threads:[~2016-04-01 15:15 UTC|newest]

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