From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] Patches for -next
Date: Wed, 02 Jun 2010 17:53:52 +0100 [thread overview]
Message-ID: <1275497632.23442.27.camel@e102109-lin.cambridge.arm.com> (raw)
In-Reply-To: <20100602164459.17783.9741.stgit@e102109-lin.cambridge.arm.com>
On Wed, 2010-06-02 at 17:48 +0100, Catalin Marinas wrote:
> Catalin Marinas (4):
> ARM: Remove the domain switching on ARMv6k/v7 CPUs
> ARM: Use lazy cache flushing on ARMv7 SMP systems
> ARM: Assume new page cache pages have dirty D-cache
> ARM: Synchronise the I and D caches via set_pte_at() on SMP systems
Forgot to mention - for easier testing, these patches are also available
in my "proposed" branch at:
http://git.kernel.org/?p=linux/kernel/git/cmarinas/linux-2.6-cm.git;a=summary
BTW, does anyone know how to get linux-arm-kernel subscribed to
patchwork.kernel.org? I know we have a patch system but that's only for
final merging rather than RFC patches.
--
Catalin
prev parent reply other threads:[~2010-06-02 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 16:48 [PATCH v2 0/4] Patches for -next Catalin Marinas
2010-06-02 16:48 ` [PATCH v2 1/4] ARM: Remove the domain switching on ARMv6k/v7 CPUs Catalin Marinas
2010-06-09 19:10 ` Nicolas Pitre
2010-06-09 22:26 ` Catalin Marinas
2010-06-10 0:56 ` Nicolas Pitre
2010-06-10 11:28 ` Catalin Marinas
2010-06-10 18:14 ` Nicolas Pitre
2010-06-10 21:00 ` Nicolas Pitre
2010-06-02 16:48 ` [PATCH v2 2/4] ARM: Use lazy cache flushing on ARMv7 SMP systems Catalin Marinas
2010-06-02 16:48 ` [PATCH v2 3/4] ARM: Assume new page cache pages have dirty D-cache Catalin Marinas
2010-06-02 16:48 ` [PATCH v2 4/4] ARM: Synchronise the I and D caches via set_pte_at() on SMP systems Catalin Marinas
2010-06-02 16:53 ` Catalin Marinas [this message]
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=1275497632.23442.27.camel@e102109-lin.cambridge.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 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).