From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/4] ARM: Move the outer_cache definitions into a separate file
Date: Tue, 23 Mar 2010 21:25:20 +0000 [thread overview]
Message-ID: <20100323212520.GD19572@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100319143300.11748.75901.stgit@e102109-lin.cambridge.arm.com>
On Fri, Mar 19, 2010 at 02:33:00PM +0000, Catalin Marinas wrote:
> To avoid #include collisions with subsequent patches in the series, this
> patch moves the outer_cache definitions to a separate asm/outercache.h
> file.
Ok.
next prev parent reply other threads:[~2010-03-23 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 14:32 [PATCH v5 0/4] ARM mandatory barriers Catalin Marinas
2010-03-19 14:33 ` [PATCH v5 1/4] ARM: Move the outer_cache definitions into a separate file Catalin Marinas
2010-03-23 21:25 ` Russell King - ARM Linux [this message]
2010-03-19 14:33 ` [PATCH v5 2/4] ARM: Add outer_cache_fns.sync function pointer Catalin Marinas
2010-03-23 21:25 ` Russell King - ARM Linux
2010-03-19 14:33 ` [PATCH v5 3/4] ARM: Add L2x0 outer_sync() support Catalin Marinas
2010-03-23 21:25 ` Russell King - ARM Linux
2010-03-19 14:33 ` [PATCH v5 4/4] ARM: Change the mandatory barriers implementation Catalin Marinas
2010-03-23 21:27 ` Russell King - ARM Linux
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=20100323212520.GD19572@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).