From: Aurelien Jarno <aurelien@aurel32.net>
To: cmchao <cmchao@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 00/12] refactor OMAP implementation
Date: Wed, 30 Jun 2010 20:42:32 +0200 [thread overview]
Message-ID: <20100630184232.GD24593@ohm.aurel32.net> (raw)
In-Reply-To: <1275321264-1131-1-git-send-email-cmchao@gmail.com>
On Mon, May 31, 2010 at 11:54:12PM +0800, cmchao wrote:
> The following changes since commit aa6f63fff62faf2fe9ffba5a789675d49293614d
> Blue Swirl:
> mc146818rtc: improve debugging
> Add a separate flag for debugging coalesced interrupts.
>
> The patches almostly base on http://meego.gitorious.org/qemu-maemo/qemu work and
> act as preparatory work to merge their OMAP3 and beagleboard support. All the
> work are to separate modules, which will be shared or extended in OMAP3 implementation
> and make some local function static
>
> change from v1 :
> 1 fix missing static declaration leading to compilation error in patch #12
> 2 rebase to newer upstream
>
> [PATCH v2 01/12] hw/omap1.c : separate gpio module
> [PATCH v2 02/12] hw/omap2.c : separate gpio module
> [PATCH v2 03/12] hw/omap2.c : separate gptimer module
> [PATCH v2 04/12] hw/omap2.c : separate synctimer module
> [PATCH v2 05/12] hw/omap2.c : separate gpmc(general purpose memory controller)
> [PATCH v2 06/12] hw/omap2.c : separate sdrc (sdram controller)
> [PATCH v2 07/12] hw/omap1.c : separate interrupt controller module
> [PATCH v2 08/12] hw/omap2.c : separate spi module
> [PATCH v2 09/12] hw/omap2.c : separate tap module(Test-Chip-level)
> [PATCH v2 10/12] hw/omwp2.c : separate l4 interconnect module
> [PATCH v2 11/12] hw/omap1.c : separate uart module
> [PATCH v2 12/12] hw/omap : make local function static and remove declaration from header
>
>
Thanks, all applied.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
prev parent reply other threads:[~2010-06-30 18:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 15:54 [Qemu-devel] [PATCH v2 00/12] refactor OMAP implementation cmchao
2010-05-31 15:54 ` [Qemu-devel] [PATCH v2 01/12] hw/omap1.c : separate gpio module cmchao
2010-05-31 15:54 ` [Qemu-devel] [PATCH v2 02/12] hw/omap2.c " cmchao
2010-05-31 15:54 ` [Qemu-devel] [PATCH v2 03/12] hw/omap2.c : separate gptimer module cmchao
2010-05-31 15:54 ` [Qemu-devel] [PATCH v2 04/12] hw/omap2.c : separate synctimer module cmchao
2010-05-31 15:54 ` [Qemu-devel] [PATCH v2 05/12] hw/omap2.c : separate gpmc(general purpose memory controller) cmchao
2010-05-31 15:54 ` [Qemu-devel] [PATCH v2 06/12] hw/omap2.c : separate sdrc (sdram controller) cmchao
2010-05-31 15:54 ` [Qemu-devel] [PATCH v2 07/12] hw/omap1.c : separate interrupt controller module cmchao
2010-05-31 15:54 ` [Qemu-devel] [PATCH v2 08/12] hw/omap2.c : separate spi module cmchao
2010-05-31 15:54 ` [Qemu-devel] [PATCH v2 09/12] hw/omap2.c : separate tap module(Test-Chip-level) cmchao
2010-05-31 15:54 ` [Qemu-devel] [PATCH v2 10/12] hw/omwp2.c : separate l4 interconnect module cmchao
2010-05-31 15:54 ` [Qemu-devel] [PATCH v2 11/12] hw/omap1.c : separate uart module cmchao
2010-05-31 15:54 ` [Qemu-devel] [PATCH v2 12/12] hw/omap : make local function static and remove declaration from header cmchao
2010-06-30 18:42 ` Aurelien Jarno [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=20100630184232.GD24593@ohm.aurel32.net \
--to=aurelien@aurel32.net \
--cc=cmchao@gmail.com \
--cc=qemu-devel@nongnu.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).