From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64 fixes for 3.16
Date: Sat, 5 Jul 2014 12:30:56 +0100 [thread overview]
Message-ID: <20140705113050.GA28232@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below for 3.16. Thanks.
The following changes since commit 4c834452aad01531db949414f94f817a86348d59:
Linux 3.16-rc3 (2014-06-29 14:11:36 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
for you to fetch changes up to 974c8e450b9327a03453a4a450a2030b1bd42b5f:
arm64: fix el2_setup check of CurrentEL (2014-07-04 16:16:52 +0100)
----------------------------------------------------------------
ARM64 fixes:
- Exception level check at boot time (for completeness, not triggering
any bug before)
- I/D-cache synchronisation logic for huge pages
- Config symbol typo
----------------------------------------------------------------
Marc Zyngier (1):
arm64: fix el2_setup check of CurrentEL
Steve Capper (2):
arm64: mm: Fix horrendous config typo
arm64: mm: Make icache synchronisation logic huge page aware
arch/arm64/include/asm/pgtable.h | 2 +-
arch/arm64/include/asm/ptrace.h | 4 ++++
arch/arm64/kernel/efi-entry.S | 3 +--
arch/arm64/kernel/head.S | 3 +--
arch/arm64/mm/flush.c | 3 ++-
5 files changed, 9 insertions(+), 6 deletions(-)
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64 fixes for 3.16
Date: Sat, 5 Jul 2014 12:30:56 +0100 [thread overview]
Message-ID: <20140705113050.GA28232@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below for 3.16. Thanks.
The following changes since commit 4c834452aad01531db949414f94f817a86348d59:
Linux 3.16-rc3 (2014-06-29 14:11:36 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
for you to fetch changes up to 974c8e450b9327a03453a4a450a2030b1bd42b5f:
arm64: fix el2_setup check of CurrentEL (2014-07-04 16:16:52 +0100)
----------------------------------------------------------------
ARM64 fixes:
- Exception level check at boot time (for completeness, not triggering
any bug before)
- I/D-cache synchronisation logic for huge pages
- Config symbol typo
----------------------------------------------------------------
Marc Zyngier (1):
arm64: fix el2_setup check of CurrentEL
Steve Capper (2):
arm64: mm: Fix horrendous config typo
arm64: mm: Make icache synchronisation logic huge page aware
arch/arm64/include/asm/pgtable.h | 2 +-
arch/arm64/include/asm/ptrace.h | 4 ++++
arch/arm64/kernel/efi-entry.S | 3 +--
arch/arm64/kernel/head.S | 3 +--
arch/arm64/mm/flush.c | 3 ++-
5 files changed, 9 insertions(+), 6 deletions(-)
--
Catalin
next reply other threads:[~2014-07-05 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 11:30 Catalin Marinas [this message]
2014-07-05 11:30 ` [GIT PULL] arm64 fixes for 3.16 Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2014-07-11 18:15 Catalin Marinas
2014-07-11 18:15 ` Catalin Marinas
2014-06-18 18:26 Catalin Marinas
2014-06-18 18:26 ` Catalin Marinas
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=20140705113050.GA28232@arm.com \
--to=catalin.marinas@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.