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: fixes for -rc5
Date: Wed, 7 Oct 2015 15:20:21 +0100 [thread overview]
Message-ID: <20151007142021.GA12577@arm.com> (raw)
Hi Linus,
Please pull the following arm64 fixes for 4.3-rc5. They address a couple
of issues found with RT, a broken initrd message in the console log and
a simple performance fix for some MMC workloads. Headlines in the tag.
Thanks,
Will
--->8
The following changes since commit 049e6dde7e57f0054fdc49102e7ef4830c698b46:
Linux 4.3-rc4 (2015-10-04 16:57:17 +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 62c6c61adbc623cdacf74b8f29c278e539060c48:
arm64: replace read_lock to rcu lock in call_break_hook (2015-10-06 19:10:28 +0100)
----------------------------------------------------------------
arm64 fixes for 4.3-rc5
- A couple of locking fixes for RT kernels
- Avoid printing bogus initrd warnings when initrd isn't present
- Performance fix for random mmap file readahead
- Typo fix
----------------------------------------------------------------
Mark Rutland (1):
arm64: Don't relocate non-existent initrd
Mark Salyzyn (1):
arm64: readahead: fault retry breaks mmap file read random detection
Yang Shi (3):
arm64: debug: Fix typo in debug-monitors.c
arm64: convert patch_lock to raw lock
arm64: replace read_lock to rcu lock in call_break_hook
arch/arm64/kernel/debug-monitors.c | 23 ++++++++++++-----------
arch/arm64/kernel/insn.c | 6 +++---
arch/arm64/kernel/setup.c | 2 ++
arch/arm64/mm/fault.c | 1 +
4 files changed, 18 insertions(+), 14 deletions(-)
next reply other threads:[~2015-10-07 14:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 14:20 Will Deacon [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-16 11:58 [GIT PULL] arm64 fixes for -rc5 Will Deacon
2024-02-16 18:52 ` pr-tracker-bot
2023-10-06 7:56 Will Deacon
2023-10-06 15:15 ` pr-tracker-bot
2023-07-21 11:44 Will Deacon
2023-07-21 11:45 ` Will Deacon
2023-07-21 17:28 ` pr-tracker-bot
2022-09-11 11:37 Will Deacon
2022-09-11 19:36 ` pr-tracker-bot
2021-08-06 13:53 Will Deacon
2021-08-06 18:40 ` Linus Torvalds
2021-08-09 10:52 ` Will Deacon
2021-08-06 18:48 ` pr-tracker-bot
2021-03-25 14:54 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-25 19:13 ` pr-tracker-bot
2020-07-10 14:39 [GIT PULL] arm64 fixes " Will Deacon
2020-07-10 16:55 ` pr-tracker-bot
2020-03-06 15:12 Will Deacon
2020-03-06 20:55 ` pr-tracker-bot
2019-06-14 15:02 [GIT PULL] arm64: " Will Deacon
2019-06-14 16:20 ` pr-tracker-bot
2019-04-12 16:05 [GIT PULL] arm64 " Will Deacon
2019-04-13 17:40 ` pr-tracker-bot
2019-02-01 17:51 [GIT PULL] arm64: " Will Deacon
2019-02-02 1:00 ` pr-tracker-bot
2018-05-11 17:30 Will Deacon
2017-03-31 17:15 Will Deacon
2016-06-24 11:41 Will Deacon
2016-02-19 16:29 Will Deacon
2015-01-16 17:16 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=20151007142021.GA12577@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).