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,
	marc.zyngier@arm.com, xi.wang@gmail.com, js07.lee@gmail.com
Subject: [GIT PULL] arm64: fixes for -rc4
Date: Thu, 14 May 2015 16:48:28 +0100	[thread overview]
Message-ID: <20150514154828.GF18984@arm.com> (raw)

Hi Linus,

Please pull the following arm64 fixes for 4.1. The main change is actually
a revert, after some (currently unused) branch patching code introduced
during the merge window was found to have some problems.

Cheers,

Will

--->8

The following changes since commit 5ebe6afaf0057ac3eaeb98defd5456894b446d22:

  Linux 4.1-rc2 (2015-05-03 19:22:23 -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 4801ba338acad2e69e905e0c537e8ba2682c4e65:

  arm64: perf: fix memory leak when probing PMU PPIs (2015-05-12 16:50:21 +0100)

----------------------------------------------------------------
arm64 fixes:
- Fix potential memory leak in perf PMU probing
- BPF sign extension fix for 64-bit immediates
- Fix build failure with unusual configuration
- Revert unused and broken branch patching from alternative code

----------------------------------------------------------------
Jungseung Lee (1):
      arm64: mm: Fix build error with CONFIG_SPARSEMEM_VMEMMAP disabled

Will Deacon (2):
      Revert "arm64: alternative: Allow immediate branch as alternative instruction"
      arm64: perf: fix memory leak when probing PMU PPIs

Xi Wang (1):
      arm64: bpf: fix signedness bug in loading 64-bit immediate

 arch/arm64/kernel/alternative.c | 53 +----------------------------------------
 arch/arm64/kernel/perf_event.c  |  8 +++----
 arch/arm64/mm/dump.c            |  2 ++
 arch/arm64/net/bpf_jit_comp.c   |  2 +-
 4 files changed, 8 insertions(+), 57 deletions(-)

             reply	other threads:[~2015-05-14 15:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 15:48 Will Deacon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-13 10:29 [GIT PULL] arm64 fixes for -rc4 Will Deacon
2023-01-13 13:58 ` pr-tracker-bot
2022-09-02 11:12 Will Deacon
2022-09-02 18:30 ` pr-tracker-bot
2022-04-22 11:20 Will Deacon
2022-04-22 21:19 ` pr-tracker-bot
2021-12-03 13:19 Will Deacon
2021-12-03 18:53 ` pr-tracker-bot
2020-11-13 12:39 GIT " Will Deacon
2020-11-13 12:44 ` [GIT " Will Deacon
2020-11-13 17:25   ` Linus Torvalds
2020-07-04 13:05 Will Deacon
2020-07-05 17:35 ` pr-tracker-bot
2019-10-17 23:43 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-18  0:06 ` Linus Torvalds
2019-10-18 17:41   ` Will Deacon
2019-10-18 19:17     ` Linus Torvalds
2019-10-21  6:46       ` Ingo Molnar
2019-10-21 11:45         ` Linus Torvalds
2019-10-22  8:16         ` Uwe Kleine-König
2019-10-18  0:15 ` pr-tracker-bot
2019-10-18 20:09 ` Jayachandran Chandrasekharan Nair
2019-06-07 15:13 [GIT PULL] arm64: fixes " Will Deacon
2019-06-07 16:45 ` pr-tracker-bot
2019-04-05 17:17 [GIT PULL] arm64 " Catalin Marinas
2019-04-05 23:50 ` pr-tracker-bot
2018-09-14 16:19 [GIT PULL] arm64: " Will Deacon
2017-12-15 18:31 Will Deacon
2017-08-04 18:32 Will Deacon
2016-06-17 17:07 Will Deacon
2015-01-09 15:22 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=20150514154828.GF18984@arm.com \
    --to=will.deacon@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=js07.lee@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=xi.wang@gmail.com \
    /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).