From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64 fixes for 3.15
Date: Fri, 16 May 2014 18:17:05 +0100 [thread overview]
Message-ID: <20140516171659.GA11088@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit 89ca3b881987f5a4be4c5dbaa7f0df12bbdde2fd:
Linux 3.15-rc4 (2014-05-04 18:14:42 -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 4797ec2dc83a43be35bad56037d1b53db9e2b5d5:
arm64: fix pud_huge() for 2-level pagetables (2014-05-16 17:34:40 +0100)
----------------------------------------------------------------
- arm64 migrate_irqs() fix following commit ffde1de64012 (irqchip: Gic:
Support forced affinity setting)
- fix arm64 pud_huge() to return 0 when only 2 levels page tables are
used (__PAGETABLE_PMD_FOLDED defined and pmd_huge already covers block
entries at the first level), otherwise KVM gets confused
----------------------------------------------------------------
Mark Salter (1):
arm64: fix pud_huge() for 2-level pagetables
Sudeep Holla (1):
arm64: use cpu_online_mask when using forced irq_set_affinity
arch/arm64/kernel/irq.c | 10 +++++++---
arch/arm64/mm/hugetlbpage.c | 4 ++++
2 files changed, 11 insertions(+), 3 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: Will Deacon <will.deacon@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 3.15
Date: Fri, 16 May 2014 18:17:05 +0100 [thread overview]
Message-ID: <20140516171659.GA11088@arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit 89ca3b881987f5a4be4c5dbaa7f0df12bbdde2fd:
Linux 3.15-rc4 (2014-05-04 18:14:42 -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 4797ec2dc83a43be35bad56037d1b53db9e2b5d5:
arm64: fix pud_huge() for 2-level pagetables (2014-05-16 17:34:40 +0100)
----------------------------------------------------------------
- arm64 migrate_irqs() fix following commit ffde1de64012 (irqchip: Gic:
Support forced affinity setting)
- fix arm64 pud_huge() to return 0 when only 2 levels page tables are
used (__PAGETABLE_PMD_FOLDED defined and pmd_huge already covers block
entries at the first level), otherwise KVM gets confused
----------------------------------------------------------------
Mark Salter (1):
arm64: fix pud_huge() for 2-level pagetables
Sudeep Holla (1):
arm64: use cpu_online_mask when using forced irq_set_affinity
arch/arm64/kernel/irq.c | 10 +++++++---
arch/arm64/mm/hugetlbpage.c | 4 ++++
2 files changed, 11 insertions(+), 3 deletions(-)
--
Catalin
next reply other threads:[~2014-05-16 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 17:17 Catalin Marinas [this message]
2014-05-16 17:17 ` [GIT PULL] arm64 fixes for 3.15 Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2014-05-04 10:46 Catalin Marinas
2014-05-04 10:46 ` Catalin Marinas
2014-04-26 9:58 Catalin Marinas
2014-04-26 9:58 ` 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=20140516171659.GA11088@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.