From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9] CM's patches for the next merging window(s)
Date: Thu, 22 Jul 2010 11:03:26 +0100 [thread overview]
Message-ID: <20100722100326.GC31293@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100719133050.24290.70856.stgit@e102109-lin.cambridge.arm.com>
On Mon, Jul 19, 2010 at 02:43:57PM +0100, Catalin Marinas wrote:
> This is a series of patches I maintain in my tree at (the 'rebased'
> branch for individual patches or 'master' for a merge-friendly branch):
I think patches 2 through 9 are fine.
I think you and Tony need to discuss patch 1 - you point out that there's
an issue writing the TLS value after this change, and Tony's patches
change the way that the TLS code works. I'd like to hear that there's
no issue if both patches were to be merged.
next prev parent reply other threads:[~2010-07-22 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 13:43 [PATCH 0/9] CM's patches for the next merging window(s) Catalin Marinas
2010-07-19 13:44 ` [PATCH 1/9] ARM: Remove the domain switching on ARMv6k/v7 CPUs Catalin Marinas
2010-07-19 13:44 ` [PATCH 2/9] ARM: Assume new page cache pages have dirty D-cache Catalin Marinas
2010-07-19 13:44 ` [PATCH 3/9] ARM: Introduce __sync_icache_dcache() for VIPT caches Catalin Marinas
2010-07-19 13:44 ` [PATCH 4/9] ARM: Use lazy cache flushing on ARMv7 SMP systems Catalin Marinas
2010-07-19 13:44 ` [PATCH 5/9] ARM: Introduce *_relaxed() I/O accessors Catalin Marinas
2010-07-19 13:44 ` [PATCH 6/9] ARM: Convert L2x0 to use the IO relaxed operations Catalin Marinas
2010-07-19 13:44 ` [PATCH 7/9] ARM: Add barriers to the I/O accessors if ARM_DMA_MEM_BUFFERABLE Catalin Marinas
2010-07-19 13:44 ` [PATCH 8/9] ARM: Improve the L2 cache performance when PL310 is used Catalin Marinas
2010-07-19 13:44 ` [PATCH 9/9] ARM: Implement phys_mem_access_prot() to avoid attributes aliasing Catalin Marinas
2010-07-22 10:03 ` Russell King - ARM Linux [this message]
2010-07-22 11:47 ` [PATCH 0/9] CM's patches for the next merging window(s) 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=20100722100326.GC31293@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).