From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/8] Patches/fixes for 2.6.35
Date: Mon, 21 Jun 2010 14:19:03 +0100 [thread overview]
Message-ID: <20100621131903.GA13624@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100621102639.9353.37648.stgit@e102109-lin.cambridge.arm.com>
On Mon, Jun 21, 2010 at 11:29:29AM +0100, Catalin Marinas wrote:
> Updates from version 3 of these series:
>
> - noMMU warning patch changed by moving the CONSISTENT_* definitions to
> the CONFIG_MMU section
> - .phys_io alignment patch replaced by two patches that enforce the
> alignment in the machine_desc structures for VExpress and RealView
> - commit log added to the T2 module relocations patch
Ok.
prev parent reply other threads:[~2010-06-21 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 10:29 [PATCH v4 0/8] Patches/fixes for 2.6.35 Catalin Marinas
2010-06-21 10:29 ` [PATCH v4 1/8] ARM: Avoid the CONSISTENT_DMA_SIZE warning on noMMU builds Catalin Marinas
2010-06-21 10:29 ` [PATCH v4 2/8] ARM: The v6_dma_inv_range() function must preserve data on SMP Catalin Marinas
2010-06-21 10:29 ` [PATCH v4 3/8] ARM: Add a config option for the ARM11MPCore DMA cache maintenance workaround Catalin Marinas
2010-06-21 10:29 ` [PATCH v4 4/8] ARM: Add support for the MOVW/MOVT relocations in Thumb-2 Catalin Marinas
2010-06-21 10:29 ` [PATCH v4 5/8] ARM: Remove dummy loads from the original relocation address Catalin Marinas
2010-06-21 10:30 ` [PATCH v4 6/8] ARM: Do not compile the Thumb-2 module relocations on an ARM kernel Catalin Marinas
2010-06-21 10:30 ` [PATCH v4 7/8] ARM: VExpress: Align the machine_desc.phys_io to 1MB section Catalin Marinas
2010-06-21 10:30 ` [PATCH v4 8/8] ARM: RealView: " Catalin Marinas
2010-06-21 13:19 ` Russell King - ARM Linux [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=20100621131903.GA13624@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).