From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64 fixes for 3.12
Date: Fri, 20 Sep 2013 14:05:46 +0100 [thread overview]
Message-ID: <20130920130538.GA32098@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below for 3.12-rc. Thanks.
The following changes since commit 272b98c6455f00884f0350f775c5342358ebb73f:
Linux 3.12-rc1 (2013-09-16 16:17:51 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux-aarch64.git tags/arm64-stable
for you to fetch changes up to 25804e6a96681d5d2142058948e218999e4f547c:
arm64: Widen hwcap to be 64 bit (2013-09-20 09:56:07 +0100)
----------------------------------------------------------------
- Compat register fault reporting fix
- Documentation clarification on tagged pointers
- hwcap widened to 64-bit (user space already reading it as 64-bit)
----------------------------------------------------------------
Catalin Marinas (2):
arm64: Make do_bad_area() function static
arm64: Correctly report LR and SP for compat tasks
Steve Capper (1):
arm64: Widen hwcap to be 64 bit
Will Deacon (1):
arm64: documentation: tighten up tagged pointer documentation
Documentation/arm64/tagged-pointers.txt | 14 +++++++-------
arch/arm64/include/asm/hwcap.h | 2 +-
arch/arm64/kernel/process.c | 21 ++++++++++++++++-----
arch/arm64/kernel/setup.c | 2 +-
arch/arm64/mm/fault.c | 2 +-
5 files changed, 26 insertions(+), 15 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-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 3.12
Date: Fri, 20 Sep 2013 14:05:46 +0100 [thread overview]
Message-ID: <20130920130538.GA32098@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below for 3.12-rc. Thanks.
The following changes since commit 272b98c6455f00884f0350f775c5342358ebb73f:
Linux 3.12-rc1 (2013-09-16 16:17:51 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux-aarch64.git tags/arm64-stable
for you to fetch changes up to 25804e6a96681d5d2142058948e218999e4f547c:
arm64: Widen hwcap to be 64 bit (2013-09-20 09:56:07 +0100)
----------------------------------------------------------------
- Compat register fault reporting fix
- Documentation clarification on tagged pointers
- hwcap widened to 64-bit (user space already reading it as 64-bit)
----------------------------------------------------------------
Catalin Marinas (2):
arm64: Make do_bad_area() function static
arm64: Correctly report LR and SP for compat tasks
Steve Capper (1):
arm64: Widen hwcap to be 64 bit
Will Deacon (1):
arm64: documentation: tighten up tagged pointer documentation
Documentation/arm64/tagged-pointers.txt | 14 +++++++-------
arch/arm64/include/asm/hwcap.h | 2 +-
arch/arm64/kernel/process.c | 21 ++++++++++++++++-----
arch/arm64/kernel/setup.c | 2 +-
arch/arm64/mm/fault.c | 2 +-
5 files changed, 26 insertions(+), 15 deletions(-)
--
Catalin
next reply other threads:[~2013-09-20 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 13:05 Catalin Marinas [this message]
2013-09-20 13:05 ` [GIT PULL] arm64 fixes for 3.12 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=20130920130538.GA32098@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.