From: Catalin Marinas <Catalin.Marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] arm64 fixes for 3.8
Date: Tue, 15 Jan 2013 18:20:06 +0000 [thread overview]
Message-ID: <20130115182005.GI2011@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit 9931faca02c604c22335f5a935a501bb2ace6e20:
Linux 3.8-rc3 (2013-01-09 18:59:55 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux-aarch64.git tags/arm64-fixes
for you to fetch changes up to 72d0ac048f3ded4022cf1cc72f54073f6fcad72f:
arm64: compat: add syscall table entries for new syscalls (2013-01-15 17:15:16 +0000)
----------------------------------------------------------------
- Page protection fixes, including proper PAGE_NONE handling
- Timezone vdso sequence counting fix
- Additional compat syscall wiring
----------------------------------------------------------------
Will Deacon (4):
arm64: vdso: remove broken, redundant sequence counting for timezones
arm64: mm: only wrprotect clean ptes if they are present
arm64: mm: introduce present, faulting entries for PAGE_NONE
arm64: compat: add syscall table entries for new syscalls
arch/arm64/include/asm/pgtable.h | 36 +++++++++++++++++++----------------
arch/arm64/include/asm/unistd32.h | 7 ++++++-
arch/arm64/kernel/vdso.c | 4 ----
arch/arm64/kernel/vdso/gettimeofday.S | 2 --
4 files changed, 26 insertions(+), 23 deletions(-)
next reply other threads:[~2013-01-15 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 18:20 Catalin Marinas [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-23 17:27 [GIT PULL] arm64 fixes for 3.8 Catalin Marinas
2013-01-04 15:45 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=20130115182005.GI2011@arm.com \
--to=catalin.marinas@arm.com \
--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