From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: post merge-window fixes for 4.1
Date: Fri, 1 May 2015 10:29:45 +0100 [thread overview]
Message-ID: <20150501092945.GC1561@arm.com> (raw)
Hi Linus,
Please pull the following arm64 fixes for 4.1. Not too much here, but
we've addressed a couple of nasty issues in the dma-mapping code as well
as adding the halfword and byte variants of load_acquire/store_release
following on from the CSD locking bug that you fixed in the core.
Thanks,
Will
--->8
The following changes since commit b787f68c36d49bb1d9236f403813641efa74a031:
Linux 4.1-rc1 (2015-04-26 17:59:10 -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 8291fd04d86b97869bd34e796bcac3141b9d5432:
arm64: perf: Fix the pmu node name in warning message (2015-04-30 12:11:30 +0100)
----------------------------------------------------------------
arm64 fixes:
- Fix perf devicetree warnings at probe time
- Fix memory leak in __dma_free()
- Ensure DMA buffers are always zeroed
- Show IRQ trigger in /proc/interrupts (for parity with ARM)
- Implement byte and halfword access for smp_{load_acquire,store_release}
----------------------------------------------------------------
Andre Przywara (1):
arm64: add missing data types in smp_load_acquire/smp_store_release
Dean Nelson (1):
arm64: add missing PAGE_ALIGN() to __dma_free()
Marek Szyprowski (1):
arm64: dma-mapping: always clear allocated buffers
Sudeep Holla (1):
ARM64: Enable CONFIG_GENERIC_IRQ_SHOW_LEVEL
Suzuki K. Poulose (1):
arm64: perf: Fix the pmu node name in warning message
Will Deacon (1):
arm64: perf: don't warn about missing interrupt-affinity property for PPIs
arch/arm64/Kconfig | 1 +
arch/arm64/include/asm/barrier.h | 16 ++++++++++++++++
arch/arm64/kernel/perf_event.c | 9 +++++++--
arch/arm64/mm/dma-mapping.c | 9 ++++-----
4 files changed, 28 insertions(+), 7 deletions(-)
reply other threads:[~2015-05-01 9:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150501092945.GC1561@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).